https://postman.hubat.net). All calls in this documentation are therefore executed against an individual PDA. If you want to test and see how the authentication works, you can use our postman collection here.
x-auth-tokenin the response header, that you can use in order to extend the lifetime of the token. The automatic token renewal can be continuously applied for up to 30 days after initial authentication event.
postman.hubat.net. Having that the following redirect has to be executed:
redirectas a query parameter named
tokenquery parameter appended and containing a RS256-signed JWT token, e.g.:
applicationVersion, is the version of the app that generated the token
application, is the application id that generated the token, it must match the application that requested
iss(issuer), which is the address of the PDA that has created the token and that you should be logging in
exp(expiry) Unix timestamp the token was created, defining whether the token is still valid
iat(issued at time) Unix timestamp the token was issued, used to calculate if 30 days have lapsed since the
/publickeyendpoint of the PDA (e.g.
https://postman.hubat.net/publickey). The precise handling of tokens with asymmetric keys will depend on your library, however you need to make sure that your library supports RS256 keys.