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

Inherit AAL level from OIDC login #364

Open
5 tasks done
jonny-puma opened this issue Dec 21, 2023 · 1 comment
Open
5 tasks done

Inherit AAL level from OIDC login #364

jonny-puma opened this issue Dec 21, 2023 · 1 comment
Labels
feat New feature or request. stale Feedback from one or more authors is required to proceed.

Comments

@jonny-puma
Copy link

jonny-puma commented Dec 21, 2023

Preflight checklist

Ory Network Project

nostalgic-agnesi-otu9x8e3js

Describe your problem

When logging in with OIDC the AAL level from the OIDC login is not used by Ory to set the AAL level of the session. If you want AAL2 you need to do a second factor after the OIDC.

Describe your ideal solution

The OIDC level of the login should be read from the claims and set in the Ory session.

Workarounds or alternatives

Current solution is to do second factor after OIDC login. If the OIDC has a second factor as well the users have to do the second factor twice.

Version

network

Additional Context

No response

@jonny-puma jonny-puma added the feat New feature or request. label Dec 21, 2023
Copy link

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

  • open a PR referencing and resolving the issue;
  • leave a comment on it and discuss ideas on how you could contribute towards resolving it;
  • leave a comment and describe in detail why this issue is critical for your use case;
  • open a new issue with updated details and a plan for resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️

@github-actions github-actions bot added the stale Feedback from one or more authors is required to proceed. label Dec 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat New feature or request. stale Feedback from one or more authors is required to proceed.
Projects
None yet
Development

No branches or pull requests

1 participant