Replies: 1 comment
-
Fixed myself - found issue when debug was enabled :-) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm using config
-e SECURITY_BASIC_ENABLED=true
-e AUTH_TYPE=OAUTH2
-e AUTH_OAUTH2_CLIENT_AZURE_CLIENTID=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
-e AUTH_OAUTH2_CLIENT_AZURE_CLIENTSECRET=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
-e AUTH_OAUTH2_CLIENT_AZURE_SCOPE=openid
-e AUTH_OAUTH2_CLIENT_AZURE_CLIENTNAME=azure
-e AUTH_OAUTH2_CLIENT_AZURE_PROVIDER=azure
-e AUTH_OAUTH2_CLIENT_AZURE_ISSUERURI=https://login.microsoftonline.com/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/v2.0
-e AUTH_OAUTH2_CLIENT_AZURE_JWKSETURI=https://login.microsoftonline.com/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/discovery/v2.0/keys \
but just getting back
![image](https://private-user-images.githubusercontent.com/65540423/331256454-97dbca38-5860-4750-a7e1-c448e786b94a.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjAwNzI5MjIsIm5iZiI6MTcyMDA3MjYyMiwicGF0aCI6Ii82NTU0MDQyMy8zMzEyNTY0NTQtOTdkYmNhMzgtNTg2MC00NzUwLWE3ZTEtYzQ0OGU3ODZiOTRhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MDQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzA0VDA1NTcwMlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTJiZmMxZjIwN2Y3OTY4ZWExOWRlYTRiNmZjZDdhZDg1NGVlMjU2YjE5ODhiYTkyZjljOGJjZTYxMThlMjA3YWQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.FWQkNbeIs5v81Qh1p6cTC1X3EzgBS4_yeJG765mJeFg)
Azure app reg Authentication is setup with Web platform, Access and ID tokens and api permission for MSGraph openid scope
I haven't enabled rbac yet - users are just added directly into the application. Any advise on how to troubleshoot\fix would be gratefully appreciated.
Beta Was this translation helpful? Give feedback.
All reactions