Credential renewal continuity for application development
Disclosed herein are methods, systems, and processes for continuously renewing credentials in application development and testing environments that include application products from third-party vendors. A notification indicating that an existing credential associated with a developer account of a third-party application will expire is received via a webhook. A credential renewal request for a new set of credentials for the developer account is sent using a request method specified for the third-party application and the new set of credentials for the developer account are received within the expiration period via the webhook.
1. A computer-implemented method, comprising:
receiving, via a webhook, a notification indicating that an existing credential associated with a developer account of a third-party application will expire within an expiration period;
sending a credential renewal request for a new set of credentials for the developer account using a request method specified for the third-party application;
receiving, via the webhook, the new set of credentials for the developer account within the expiration period;
determining that the existing credential has been compromised prior to being renewed within the expiration period; and
in response to determining that the existing credential has been compromised prior to being renewed within the expiration period,
adjusting the expiration period to cause the existing credential to expire immediately, and
obfuscating the existing credential to ensure that the existing credential is not correlated to the new set of credentials.
2. The computer-implemented method of claim 1 , further comprising:
determining that the third-party application is unintegrated;
receiving an input comprising the expiration period for the existing credential;
processing a credential renewal form for the third-party application; and
sending the credential renewal request requesting the new set of credentials a pre-determined amount of time before the expiration period ends.
3. The computer-implemented method of claim 2 , further comprising:
receiving the new set of credentials; and
storing the new set of credentials in the developer account.
4. The computer-implemented method of claim 1 , wherein
the new set of credentials are received via an Application Programming Interface (API).
5. The computer-implemented method of claim 1 , wherein
the request method comprises POST.
6. The computer-implemented method of claim 2 , wherein
the expiration period is received when the existing credential is created.
7. The computer-implemented method of claim 1 , further comprising:
generating a honeypot with an instantiation of the third-party application;
sending a request to re-direct network traffic sent to the third-party application using the existing credential to the instantiation of the third-party application in the honeypot for remainder of the expiration period; and
causing access to be permitted to the third-party application only after the new set credential have been received within the adjusted expiration period.
8. A non-transitory computer readable storage medium comprising program instructions executable to:
receive, via a webhook, a notification indicating that an existing credential associated with a developer account of a third-party application will expire within an expiration period;
send a credential renewal request for a new set of credentials for the developer account using a request method specified for the third-party application;
receive, via the webhook, the new set of credentials for the developer account within the expiration period;
determine that the existing credential has been compromised prior to being renewed within the expiration period; and
in response to determining that the existing credential has been compromised prior to being renewed within the expiration period,
adjust the expiration period to cause the existing credential to expire immediately, and
obfuscate the existing credential to ensure that the existing credential is not correlated to the new set of credentials.
9. The non-transitory computer readable storage medium of claim 8 , further comprising:
determining that the third-party application is unintegrated;
receiving an input comprising the expiration period for the existing credential;
processing a credential renewal form for the third-party application;
sending the credential renewal request requesting the new set of credentials a pre-determined amount of time before the expiration period ends;
receiving the new set of credentials; and
storing the new set of credentials in the developer account.
10. The non-transitory computer readable storage medium of claim 8 , wherein
the request method comprises POST, and
the expiration period is received when the existing credential is created.
11. The non-transitory computer readable storage medium of claim 8 , further comprising:
generating a honeypot with an instantiation of the third-party application;
sending a request to re-direct network traffic sent to the third-party application using the existing credential to the instantiation of the third-party application in the honeypot for remainder of the expiration period; and
causing access to be permitted to the third-party application only after the new set credential have been received within the adjusted expiration period.
12. A system comprising:
one or more processors; and
a memory coupled to the one or more processors, wherein the memory stores program instructions executable by the one or more processors to:
receive, via a webhook, a notification indicating that an existing credential associated with a developer account of a third-party application will expire within an expiration period;
send a credential renewal request for a new set of credentials for the developer account using a request method specified for the third-party application;
receive, via the webhook, the new set of credentials for the developer account within the expiration period;
determine that the existing credential has been compromised prior to being renewed within the expiration period; and
in response to determining that the existing credential has been compromised prior to being renewed within the expiration period,
adjust the expiration period to cause the existing credential to expire immediately, and
obfuscate the existing credential to ensure that the existing credential is not correlated to the new set of credentials.
13. The system of claim 12 , further comprising:
determining that the third-party application is unintegrated;
receiving an input comprising the expiration period for the existing credential;
processing a credential renewal form for the third-party application;
sending the credential renewal request requesting the new set of credentials a pre-determined amount of time before the expiration period ends;
receiving the new set of credentials; and
storing the new set of credentials in the developer account.
14. The system of claim 12 , wherein
the new set of credentials are received via an Application Programming Interface (API),
the request method comprises POST, and
the expiration period is received when the existing credential is created.
15. The system of claim 12 , further comprising:
generating a honeypot with an instantiation of the third-party application;
sending a request to re-direct network traffic sent to the third-party application using the existing credential to the instantiation of the third-party application in the honeypot for remainder of the expiration period; and
causing access to be permitted to the third-party application only after the new set credential have been received within the adjusted expiration period.