Start of change

Global authentication cache

DB2® can cache user credentials when processing remote TCP/IP connections.

When processing a TCP/IP connection, DB2 authenticates a user ID by using RACF®. If the user ID is successfully authenticated, DB2 caches the user credentials for three minutes during which DB2 reuses the cached credentials for subsequent connection requests from the same user ID. DB2 deletes the cache entries if the password is changed through a DRDA password change request.

DB2 does not differentiate PassTickets from passwords while caching user credentials.

End of change