Access tokens are issued as part of the OAuth 2.0 protocol, to provide temporary access to a third party app (the client) on behalf of a member.
This page lets you review the access tokens that have been issued recently. They include:
When reviewing the tokens, pay particular attention to the client ID, member ID and any unusual long lifetime.
There are two methods to remove tokens depending on whether they have expired or not.
Click Revoke to remove from memory. This immediately revokes access to the bearer and renders this token unusable.
Click Purge... to remove from memory all the tokens which have already expired. This has no effect on the bearer since the token has already expired, but it frees some memory and removes these tokens from the table.
Creating access tokens manually bypasses the OAuth 2.0 protocol and is inherently unsafe. For security reasons, this functionally might be conditionally removed in future versions of PageSeeder.
Access tokens are created as part of the OAuth 2.0 protocol following one of the predefined authorization flows. They usually require the client or member to authenticate.
But, as an administrator, you can issue an access token for testing by clicking the
The only scopes that PageSeeder supports at the moment are:
For example, “openid profile email” returns the user details, including the email, following the format defined by OpenID.
Administration menu >
The PageSeeder user manual
© Allette Systems (Australia)