An unauthenticated scan tests your login page and very little else. Auth profiles are saved sets of credentials that Vooki Pro attaches to scan traffic, reusable across every scan and schedule for an application. If a token changes, you edit one profile instead of every scan that used it.
| Type | What it sends |
|---|---|
| Bearer Token | Authorization: Bearer <token> |
| Basic Auth | Username and password as an Authorization header |
| API Key | A key in the header or parameter your API expects |
| Cookie | One or more cookies, for example sessionid=abc; csrftoken=xyz |
| OAuth2 Client Credentials | Vooki Pro fetches a token from your token endpoint using the client ID, secret and scope, so you are not pasting a token that expires in an hour |
SSO or a complicated login? Record yourself logging in (see browser recordings) and choose Create a cookie auth profile from the recording. You can also pick Login via recording directly on the scan's Auth step.
auth block. Replace secrets with ${ENV_VAR} placeholders.*/logout), or the scanner will log itself out mid-scan.Full reference: Auth profiles (docs)