Signals Notebook: Can I continue using the same Bearer Token Client ID and Redirect URLs after switching to PKCE Authorization Code Flow?

Question

My Signals Notebook tenant has been integrated with an external app via a short-term bearer token, using the OAuth Implicit Flow. Since Signals Notebook has supported the OAuth Authorization Code Flow with PKCE (Proof Key for Code Exchange) since v26.3, I will switch integration via the Authorization Code Flow with PKCE.

Can I continue using the same Client ID and Redirect URLs for the Authorization Code Flow with PKCE?

Answer

Yes, you can continue using the same short-term bearer token configuration for your Signals Notebook tenant. Your Client ID and Redirect URLs will continue to work with the Authorization Code Flow. 

To update your integration for the Authorization Code Flow, you will need to use the Token Endpoint, which is not needed for the Implicit Flow. The following URL should work as your Token Endpoint if you already have bearer token configuration enabled for the tenant.

Token URL: <Tenant URL>/auth/oauth/token 
   (e.g., https://my_tenant_name.signalsresearch.revvitycloud.com/auth/oauth/token)

Even after you switch to the Authorization Code Flow, the current Implicit Flow continues working.