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
I am working on a project where one type of user will publish the container applications and other type of user will use those container application. To store the container application we are using Harbor. The project has other functionalities as well. To manage the user of project we are using Keycloak. We have integrated the Harbor with keycloak using the below document https://goharbor.io/docs/2.6.0/administration/configure-authentication/oidc-auth/
The problem is that this doc mentioned to use the UI to onbaord a user however we are not exposing the harbor UI. We are only using the harbor backend. The API /c/oidc/onboard, which is responsible for onboarding a oauth user is meant for browser only flow.
Can we have another similar API for backend flow which works with basic auth or JWT token instead of x-csfr-token?
The text was updated successfully, but these errors were encountered:
ashishkumar-07
changed the title
Onboard an Oauth user via API
Onboard an OIDC user via API
Aug 31, 2022
I am working on a project where one type of user will publish the container applications and other type of user will use those container application. To store the container application we are using Harbor. The project has other functionalities as well. To manage the user of project we are using Keycloak. We have integrated the Harbor with keycloak using the below document
https://goharbor.io/docs/2.6.0/administration/configure-authentication/oidc-auth/
The problem is that this doc mentioned to use the UI to onbaord a user however we are not exposing the harbor UI. We are only using the harbor backend. The API
/c/oidc/onboard
, which is responsible for onboarding a oauth user is meant for browser only flow.Can we have another similar API for backend flow which works with basic auth or JWT token instead of x-csfr-token?
The text was updated successfully, but these errors were encountered: