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
If rest-api requests get 401, or web requests are forwarded to the login page, I issue an access token via our oauth2 server (keycloak) and inject it as bearer token in the header. This works fine, but it is single threaded and quite slow.
Are there ways in linkchecker to do this?
on 401 responses:
curl -i -H "Content-Type: application/x-www-form-urlencoded" -X POST "https://auth.example.com/auth/realms/<REALM>/protocol/openid-connect/token" -d "grant_type=client_credentials&client_id=<CLIENTID>&client_secret=<CLIENTSECRET>"
this will return an accesstoken in json, I can extract
If rest-api requests get 401, or web requests are forwarded to the login page, I issue an access token via our oauth2 server (keycloak) and inject it as bearer token in the header. This works fine, but it is single threaded and quite slow.
Are there ways in linkchecker to do this?
on 401 responses:
this will return an accesstoken in json, I can extract
and then inject it into the requests header:
The text was updated successfully, but these errors were encountered: