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

Extract OIDC implementation into its own artifact #320

Open
kalgon opened this issue Mar 16, 2022 · 4 comments
Open

Extract OIDC implementation into its own artifact #320

kalgon opened this issue Mar 16, 2022 · 4 comments

Comments

@kalgon
Copy link

kalgon commented Mar 16, 2022

As far as I can see, the OIDC package is pretty well isolated and does not depend on other internal Soteria classes (except for org.glassfish.soteria.Utils). Wouldn't it be possible to extract this module into its own artifact so that it can be embedded directly into the application? I'm using the version of Soteria that comes with my application server (JBoss EAP) and I don't know when it will be updated with a version of Soteria that contains OIDC.

@arjantijms
Copy link
Contributor

For that purpose, this one is probably beter suited:

https://github.com/payara/ecosystem-security-connectors

@kalgon
Copy link
Author

kalgon commented Apr 27, 2022

Well, I tried to use the payara openid-standalone on JBoss EAP but it fails (probably) because of this line. I am redirected in a loop to /org.jboss.resteasy.specimpl.ResteasyUriBuilder@XXX. The authUrl should be built using UriBuilder.build() instead of toString().

@kalgon
Copy link
Author

kalgon commented Apr 27, 2022

I made a PR for payara but the same problem seems to be present in soteria as well.

@arjantijms
Copy link
Contributor

Thanks @kalgon! I'll take a look at this very soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants