Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Map out challenges related to access management and caching in Auth #2963

Open
cammiida opened this issue Feb 3, 2025 · 0 comments
Open
Assignees
Labels
kind/analysis status/draft Status: When you create an issue before you have enough info to properly describe the issue. status/triage

Comments

@cammiida
Copy link
Contributor

cammiida commented Feb 3, 2025

Description

User authorization is cached for 10 minutes today. That means that if a user is delegated access to a form and has logged in within the last 10 minutes, the user will be met with a "you do not have access" when opening the form in question. This is most prominent when testing, but can also apply to eager users that is currently "working in Altinn".

Does this also apply to the person instantiating the form? Let's say that person has write, but not sign from policy.xml, but then delegates sign rights to themself. What happens?

In scope

No response

Out of scope

No response

Additional Information

No response

Analysis

No response

Conclusion

No response

@cammiida cammiida added kind/analysis status/draft Status: When you create an issue before you have enough info to properly describe the issue. labels Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/analysis status/draft Status: When you create an issue before you have enough info to properly describe the issue. status/triage
Projects
Status: No status
Development

No branches or pull requests

2 participants