Store provider credentials for the right environment

This page is available only to DealJourney platform administrators.

In Tilgangsopplysninger, choose Miljø hos leverandøren to find credentials for production, staging, demo, test or development. This describes the credentials at the provider, not where DealJourney has deployed them. The filter also includes Delt mellom miljøer and Uspesifisert. Shared credentials are a separate explicit choice; unspecified older entries are never assumed to be production credentials.

Choose Legg til tilgangsopplysninger and open Leverandør. Choose an existing provider, or choose Legg til leverandør at the bottom of the dropdown, enter Leverandørnavn and confirm. You can also type a new name in the search field and choose the matching create action.

Choose the provider's environment. The info button Hjelp til å velge miljø explains the choice without guessing from a key. A specific environment filter carries into the form; otherwise you must choose one. For Navn hos leverandøren, copy the provider's wording, such as application key, subscription key, apiUser or companyApiGuid. Paste the corresponding protected Verdi. Use Legg til en verdi til for each additional value supplied. Values can contain multiple lines, including JSON or certificates. You do not need to decide whether a value is an API key, login or another kind of secret, or know DealJourney's internal deployment variable names.

Use Privat for meg if only you should see the entries; otherwise they are shared with other platform administrators. Choose Lagre. Each value is stored as an encrypted entry under the provider and environment. If some entries fail, their values stay in the form and Prøv resterende igjen saves only those entries. Saved entries are not submitted again. Closing the form discards unsaved values.

For an ENV-style list, expand Lim inn flere verdier and paste one label=value pair per line. Quote values containing multiple lines. Choose Klargjør felter to review the resulting fields before saving. Any unsupported line, empty value or duplicate label rejects the paste rather than silently dropping it. JSON credentials can be pasted intact into one protected value; the form does not guess how to split a JSON object into separate entries.

When editing an existing entry, a blank Ny verdi (la stå tomt for å beholde gjeldende) preserves its stored value. Existing login details and deployment mappings remain available in Eksisterende detaljer. Never place a secret in ordinary notes or labels.

Saving credentials does not deploy, activate or verify them. The separate Rotasjonshistorikk for staging and Rotasjonshistorikk for produksjon views record rotations; they are not alternative credential stores.