Release Notes
The new version introduces Personal Access Tokens.
Personal Access Tokens (PATs) can be used to authenticate against Netbird’s Public API (coming soon).
Users can create as many tokens for themself as they need. Each token requires the user to set how long the token will be valid, we support token expiration between 1 and 365 days; after that, the token will be rejected.
All users can now access the Personal Settings section under the Dashboard > Settings tab. This section shows an overview of all the Personal Access Tokens belonging to a user, when they were created, when they were last used to authenticate, and when they will expire.
When adding a new token, you must provide a name and specify how long the token should be valid.
After successfully creating the token you will see the token in plain text to copy and store in a secure location. Once you close the window, there is no way to retrieve the plain token again.
You can use the new token to send API requests to the management API by adding the header Authorization: Token NEW_TOKEN, below you have an example of a request to the peer's endpoint of our Public API:
curl 'https://api.wiretrustee.com/api/users' -X GET -H "Authorization: Token nbp_61efTM2ZvmiLpaOa5mpx1MLnL5zXc13bcMhm”More API documentation will come soon!
Management
- Add API authentication with PATs (#774)
- Add activity events (#776)
- Add disable let's encrypt and traefik template (#747)
- Add token source and device flow audience variables (#780)
- Check multiple audience values (#781)
Client
Dashboard
- Use ID token payload when oidcUser is nil (netbirdio/dashboard#127)
- Handle additional activity events (netbirdio/dashboard#128)
- Feat add custom id claim (netbirdio/dashboard#129)
- Use peerID in the Routes view (netbirdio/dashboard#130)