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
⚠️ Please verify that this feature request has NOT been suggested before.
I checked and didn't find similar feature request
🏷️ Feature Request Type
Other
🔖 Feature description
At the moment you can use basic auth and ntlm to authenticate against http endpoints.
To monitor the availability of APIs it would be helpful to have the additional alternative with the OIDC Client Credentials Grant
✔️ Solution
request a jwt token and add it as bearer header to oidc protected http endoints
So my suggestion would be that if you select OIDC Client Credentials Grant as auth method in the UI you receive the following input fields
Mandatory:
Token Endpoint
Client Id
Client Secret
Optional:
Scope
Audience
Then before the actual http call is triggered a jwt token is requested and added to the http header.
Because the response of the grant flow should also contains an expire time the token can be cached.
❓ Alternatives
I'm aware that the push monitor would be alternative possibility but would be nice to handle the checks with a build in functionality
📝 Additional Context
I would also be willing to provide a PR for the topic
The text was updated successfully, but these errors were encountered:
@ste1nstone #3119 was merged, but we accidentally left this issue open.
Could you please close this issue?
PS: @hegerdes The next time please add Fixes #issuenumber as a literal string (github only understand one issue per fixes) as requested in #3119 (comment)
The reason is that otherwise resolved issues are not getting closed ^^
🏷️ Feature Request Type
Other
🔖 Feature description
At the moment you can use basic auth and ntlm to authenticate against http endpoints.
To monitor the availability of APIs it would be helpful to have the additional alternative with the OIDC Client Credentials Grant
✔️ Solution
request a jwt token and add it as bearer header to oidc protected http endoints
Most of the providers (I checked KeyCloak, AWS Cognito and Azure AD) implement the client credential flow according to the standard https://www.rfc-editor.org/rfc/rfc6749#section-4.4
Auth0 as another big provider adds an additional field to the request with audience
So my suggestion would be that if you select OIDC Client Credentials Grant as auth method in the UI you receive the following input fields
Mandatory:
Optional:
Then before the actual http call is triggered a jwt token is requested and added to the http header.
Because the response of the grant flow should also contains an expire time the token can be cached.
❓ Alternatives
I'm aware that the push monitor would be alternative possibility but would be nice to handle the checks with a build in functionality
📝 Additional Context
I would also be willing to provide a PR for the topic
The text was updated successfully, but these errors were encountered: