Skip to main content
Coming in the first release. This page describes behaviour being built for the first Gliss release. Details may change before it ships.

​
Requesting a secret

Your AI declares each secret’s name and type in capabilities.secrets, then asks Gliss for a secret request. Gliss returns a link, never a field for a value.
  • Send the link to whoever holds the value. Often that is not you, but, for example, the Salesforce admin.
  • The link works once, for up to 72 hours.
  • The page is on your company’s own domain. The browser encrypts the value to a key in your company’s AWS account. Nothing passes through Gliss cloud, not even encrypted.
  • A guest outside your company may set a credential secret if your catalog allows guest links. Only signed-in members may set an endpoint secret.

​
Mock mode

A missing secret does not stop Preview or Beta. The app starts, and GLISS_MISSING_SECRETS lists the secrets that are not set yet. The console shows the app as running in mock mode. Write the app so each integration fakes its responses while its secret is missing. Your AI does this when it follows the guidance Gliss adds to the repository. A missing secret does block Publish. Live needs every secret it declares.