Browse Prior Art Database

Method and System for Updating a Functional Account Password with Zero Downtime

IP.com Disclosure Number: IPCOM000244865D
Publication Date: 2016-Jan-22
Document File: 2 page(s) / 46K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method and system is disclosed for updating a functional account password with zero down time by utilizing two or more functional accounts with identical privileges but with offset expiration.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 2

Method and System for Updating a Functional Account Password with Zero Downtime

Disclosed is a method and system for updating a functional account password with zero down time by utilizing two or more functional accounts with identical privileges but with offset expiration. The at least two functional accounts contain dynamically varying tokens, wherein the tokens are used to automatically identify and access a stored

appropriate functional account and a respective one or more credentials of a user which dynamically offsets expiration.

The automated processes implemented in the method and system use a storage mechanism such as, but not limited to, a database, a key store, a password file to store user credentials. The automated processes also use a provided token to identify which account information to use.

Prior to an account expiring, credentials for a new account are added to the storage. The automated processes are then provided a token associated with credentials for the new account and the automated processes start using the new account for authenticating. Once all known automated processes are using the new account for authenticating, a password can be changed on an original account. Any rogue

processes using the original account may cause it to be locked out, but it would not affect any process using the new account. Once lockout issues have been resolved, the original account can be reused when an in-use account expires.

In one implementation, the authentication credentials could be stored in a JSON array as follows.

[

 { "token" : "NZ2HLPXTUO", "username" : "account1", "password" : "GJ8ALYT008GVCK2ST5W3" },

 { "token" : "K8FG01M09W", "username" : "account2", "password" : "T4HY02E7RFW09HHXT9KV" },

 { "token" : "FOBA0ZXRGV", "username" : "account1", "password" : "M29GW4ACW7004ND2I4TR" }
]

T...