-
Notifications
You must be signed in to change notification settings - Fork 6k
Provide support for SAML 2.0 and JWT Profile #4906
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
Comments
Related specs: JSON Web Token (JWT) Profile -- This is a priority feature for UAA -- |
Are there any plans to implement this in the near future? |
@lukas-stadler We'll look at getting this in for the 5.2 release. |
I'm interested in work at this issue, can someone guide me on what files/classes should be touched? |
Thanks for the offer @wagnerluis1982. This issue is made up of 2 separate features - JWT and SAML Profile. Which one are you interested in? |
@jgrandja I have some experience with JWT, but for now I prefer SAML for the opportunity to learn. |
@wagnerluis1982 I'm not entirely convinced if we need to provide support for SAML 2.0 Profile. I just logged #7581 so we can track the upvotes for this feature. Let's hold off for now until we see there is a demand for this feature. Is there any other issue/task you would be interested in? |
@jgrandja understood, IMO is a good move, about another issue, not now, but I'll stick around. |
Client-side support would enable app developers to begin consuming these flows, which UAA already supports from the Authorization Server side for Cloud Foundry. We've seen growing interest in enabling this use case as a way to integrate with legacy applications and with applications using a different OAuth2 identity provider.
The text was updated successfully, but these errors were encountered: