Before a third-party application can be connected to Gotham, it must be registered on the platform.
The initial registration process creates a name, a client ID, and a client secret for the third-party application; see the OAuth.com docs for more information on client IDs and client secrets, which are used in the authorization workflow.
Then, a third-party application will need to be configured with a redirect URL for the authorization process, as well as a name, description, and icon which are used for the in-platform representation of the third-party application.
If using a confidential client, you must copy the client secret at this point. The secret will not be available again after leaving this page. If you lose access to the client secret, you will need to rotate the secret.