Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved


Chapter 13 OAuth Server : Access Token Persistence

Access Token Persistence
The OAuth server uses ActiveSpaces as caching and persistence layer. The access tokens are persisted in the database or memory. Use the database in production systems to store the access tokens. If you choose the memory to store the access tokens, they are lost if the OAuth server goes down.
To use ActiveSpaces for access tokens persistence, follow these steps:
1.
2.
3.
On the home page of the Config UI, select the Gateway Engine Properties from the drop-down list.
4.
Click the Security link.
5.
6.
You can set the following properties for OAuth Data Space in ASG_CONFIG_HOME/asg.properties file:
The default value is ASG-OAuth-Tokens
For example, tcp://machine1_IP_Address:6300;machine2_IP_Address:6300
For example, tcp://machine1_IP_Address:6300
If the Database is set, define the properties for database server connection.
Specifies the expiration time (in minutes) for an access token. The default value is 60 minutes. When the access token passes expiration time as specified by this property, it is no longer valid but still remains in the database. The access token is removed from the database based on the value specified by the tibco.clientVar.oauth.access.token.space.ttl property.
Specifies the retention period (in minutes) for an access token. The default value is 1440 minutes (1 day) . When the access token passes retention period as specified by this property, the token is removed from the database. By default, the access token is removed from the database after 1 day.

Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved