Vault OIDC identity provider web UI redirect doesn't work on Android (Chrome) after authenticating with Google OIDC #184
Assignees
Labels
bug
Something isn't working
Comments
siepkes
added a commit
to siepkes/openbao
that referenced
this issue
Mar 7, 2024
This fixes the issue when having an Android app authenticate with the OpenBoa OIDC identity provider and having OpenBao in turn authenticate the user with Google OIDC the redirect back to the Android app from OpenBao doesn't work. So after logging in with Google you get correctly redirected to OpenBao but then OpenBAO doesn't redirect back to the app. Chrome (104) on Android would show the logo loading animation forever. This code was originally developed by @prajnamohan1 while working at Service Planet Rotterdam B.V.. I, Jasper Siepkes, in my capacity of IT Manager at Service Planet Rotterdam B.V. herby grant permission to use this code under the MPL-2.0 license. Resolves: openbao#184
siepkes
added a commit
to siepkes/openbao
that referenced
this issue
Mar 7, 2024
This fixes the issue when having an Android app authenticate with the OpenBoa OIDC identity provider and having OpenBao in turn authenticate the user with Google OIDC the redirect back to the Android app from OpenBao doesn't work. So after logging in with Google you get correctly redirected to OpenBao but then OpenBAO doesn't redirect back to the app. Chrome (104) on Android would show the logo loading animation forever. This code was originally developed by @prajnamohan1 while working at Service Planet Rotterdam B.V.. I, Jasper Siepkes, in my capacity of IT Manager at Service Planet Rotterdam B.V. herby grant permission to use this code under the MPL-2.0 license. Resolves: openbao#184
siepkes
added a commit
to siepkes/openbao
that referenced
this issue
Mar 7, 2024
This fixes the issue when having an Android app authenticate with the OpenBoa OIDC identity provider and having OpenBao in turn authenticate the user with Google OIDC the redirect back to the Android app from OpenBao doesn't work. So after logging in with Google you get correctly redirected to OpenBao but then OpenBAO doesn't redirect back to the app. Chrome (104) on Android would show the logo loading animation forever. This code was originally developed by @prajnamohan1 while working at Service Planet Rotterdam B.V.. I, Jasper Siepkes, in my capacity of IT Manager at Service Planet Rotterdam B.V. herby grant permission to use this code under the MPL-2.0 license. Resolves: openbao#184 Signed-off-by: Jasper Siepkes <siepkes@serviceplanet.nl>
siepkes
added a commit
to siepkes/openbao
that referenced
this issue
Mar 7, 2024
This fixes the issue when having an Android app authenticate with the OpenBoa OIDC identity provider and having OpenBao in turn authenticate the user with Google OIDC the redirect back to the Android app from OpenBao doesn't work. So after logging in with Google you get correctly redirected to OpenBao but then OpenBAO doesn't redirect back to the app. Chrome (104) on Android would show the logo loading animation forever. This code was originally developed by @prajnamohan1 while working at Service Planet Rotterdam B.V.. I, Jasper Siepkes, in my capacity of IT Manager at Service Planet Rotterdam B.V. herby grant permission to use this code under the MPL-2.0 license. Resolves: openbao#184 Signed-off-by: Jasper Siepkes <siepkes@serviceplanet.nl>
naphelps
pushed a commit
that referenced
this issue
Mar 7, 2024
This fixes the issue when having an Android app authenticate with the OpenBoa OIDC identity provider and having OpenBao in turn authenticate the user with Google OIDC the redirect back to the Android app from OpenBao doesn't work. So after logging in with Google you get correctly redirected to OpenBao but then OpenBAO doesn't redirect back to the app. Chrome (104) on Android would show the logo loading animation forever. This code was originally developed by @prajnamohan1 while working at Service Planet Rotterdam B.V.. I, Jasper Siepkes, in my capacity of IT Manager at Service Planet Rotterdam B.V. herby grant permission to use this code under the MPL-2.0 license. Resolves: #184 Signed-off-by: Jasper Siepkes <siepkes@serviceplanet.nl>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When having an Android app authenticate with the OpenBao OIDC identity provider and having OpenBao in turn authenticate the user with Google OIDC the redirect back to the Android app from OpenBao doesn't work. So after logging in with Google you get correctly redirected to OpenBao but then OpenBao doesn't redirect back to the Android app. Chrome (104) on Android will show the OpenBao logo loading animation forever.
When the user uses an Android app to authenticate via the OpenBao OIDC identity provider and directly authenticates to OpenBao with for example the
userpassauthentication method the user does get correctly redirected back to the Android app.When the user tries to login to the OpenBao web UI directly with Google OIDC this also works correctly.
So the problem only occurs when one tries to authenticate in an Android app and uses the OpenBao OIDC provider which then in turn uses Google OIDC (and perhaps other OIDC providers) authentication.
The text was updated successfully, but these errors were encountered: