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
Is your feature request related to a problem? Please describe.
I would want to check pages that can only respond with a 200 after authentication.
It would need to be ensured that tokens are sent only to the sites they belong to.
Also, credentials shouldn't be stored as plain text in a configuration file.
Describe the solution you'd like
I would like to see the possibility to provide a configuration like that:
auth:
- site: <some site URL pattern>authType: basicuserByEnvvar: <some envvar holding a user name>tokenByEnvvar: <some envvar holding a token>
- site: <some other site URL pattern>authType: oauth2userByShellCommand: /path/to/my/script/retrieve-user.shtokenByShellCommand: /path/to/my/script/retrieve-token.sh
Describe alternatives you've considered
There could be dozens of secret sources or auth types, but starting with reading credentials via envvars and allow basic and oauth2 authentication should provide a valuable first iteration.
Maybe in addition something like this might be suitable:
Is your feature request related to a problem? Please describe.
I would want to check pages that can only respond with a 200 after authentication.
It would need to be ensured that tokens are sent only to the sites they belong to.
Also, credentials shouldn't be stored as plain text in a configuration file.
Describe the solution you'd like
I would like to see the possibility to provide a configuration like that:
Describe alternatives you've considered
There could be dozens of secret sources or auth types, but starting with reading credentials via envvars and allow basic and oauth2 authentication should provide a valuable first iteration.
Maybe in addition something like this might be suitable:
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: