Browser sessions are for interactive (web-flow) use cases. Personal access tokens can be used to access the Pipeline API in a programatic way. They are named, can have an expiry date, if not defined they never expire. Tokens can be also deleted of course. A user can have any number of tokens.
Personal access tokens on the UI are available under the settings page:
https://{PIPELINE_HOST}/ui/{USERNAME}/settings
Note: The browser session cookies are expiring API tokens as well, thus you will see your browser sessions listed also on this page.
When creating a new personal access token a name has to be set, this useful for identifying the it later on (this is a mandatory field). Also an optional expiration date can be defined, which is the date until the token is valid and can be used, if it expires the token gets deleted and can’t be used to access the Pipeline API.
Note: In the background a new token is created via
POST-ing an HTTP request to thehttp://{PIPELINE_HOST}/pipeline/api/v1/tokensendpoint.
The newly generated token value is visible only until you navigate away from the tokens page for security reasons.
Next steps 🔗︎
With the token, you can log in to the Banzai CLI in a non-interactive session.
