just checking, could be a bug: there seems to be only one .well-known oidc url for the whole site. However, when using a different cert than the built-in one for an application this does not work, or am I missing something?
Wouldn't each app need its own oidc url endpoint? And isn't it better to create per-app certs instead of using the same cert across apps with potentially different tenants by default? Not an expert, hence asking and looking forward to more knowledgeable input.
On my list, will do!
Is there a auto-signUP? The expected behavior I was also looking for is:
- no user account exists
- user enters email
- confirms code received in email
- user is logged in directly
actual behavior:
- when using the sign-in page, you get an error user does not exist
- on sign up page, you can configure it to not require password, the user account is created, but the user is not logged in even with "auto signIN" enabled on the application. you get a page "user has been created successfully, with link to sign in, where user has to once again do an email verification loop and is not immediately signed up and signed in which would be ok.
@hsluoyz is using the enterprise hosted version the best way to support the project? what's the situation there, is it still going?
Hi there, thank you in advance for your help!
I'm trying to use OAuth endpoint with response_type=token&response_mode=query :
https://ENDPOINT/login/oauth/authorize?client_id=CLIENT_ID&response_type=token&response_mode=query
My client app requires a redirect to REDIRECT_URI/?access_token=...
but I'm always getting the fragment response mode regardless: REDIRECT_URI/#access_token=...
Very possible I'm missing something so thanks for your understanding! But when changing the redirect url manually to have a query parameter it works as expected and the spec reads like this should be possible: https://openid.net/specs/oauth-v2-multiple-response-types-1_0.html#ResponseModes
