You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, here is another bug that I discovered while was trying to add OIDC Keycloak from UI Admin console in Boundary.
If you add issuer with .well-known/openid-configuration, in my example it is http://172.21.33.27:9999/realms/inventory/.well-known/openid-configuration:
And fill out the rest, you'll be able to add the OIDC Provider as expected, but, once you'll try to set it's state for example Public, it will fail:
Cuz the boundary set the issuer as - http://172.21.33.27:9999/realms/inventory/ - with the trailing slas in the end, and with "/" it does not match with the OIDC provider which is:
It doesn't include **/**
To resolve this issue you just need to delete that slash and the OIDC can be set to Public and after been used without any problems:
The text was updated successfully, but these errors were encountered:
Hi, here is another bug that I discovered while was trying to add OIDC Keycloak from UI Admin console in Boundary.
If you add issuer with
.well-known/openid-configuration
, in my example it ishttp://172.21.33.27:9999/realms/inventory/.well-known/openid-configuration
:And fill out the rest, you'll be able to add the OIDC Provider as expected, but, once you'll try to set it's state for example Public, it will fail:
Cuz the boundary set the issuer as - http://172.21.33.27:9999/realms/inventory/ - with the trailing slas in the end, and with "/" it does not match with the OIDC provider which is:
It doesn't include
**/**
To resolve this issue you just need to delete that slash and the OIDC can be set to Public and after been used without any problems:
The text was updated successfully, but these errors were encountered: