From current documentation in both the Release and Deploy tooling, you can only create Personal Access Tokens (PAT) through the UI of each tool.

We need this both for developing automation around updating/creating PATs that we will be used by Connections in release tasks. It is also necessary since JSESSION/SESSION_XLD type cookies no longer work as we move OIDC/SSO in our tools. Many of our internal maintenance and change processes utilize the REST API via LDAP authentication, using headless/generic service user accounts, that are external to the Deploy/Release instances.

This would be valuable so users of your tools can handle managing their PATs through automation and try to update various Connections made in the Release tooling as needed when PATs begin to expire.

by: Bryan G. | 15 days ago | API & CLI tools