Toggle navigationAirlock Secure Access HubAbout this documentAbout Airlock IAMIAM 8.1 release notesSecurity best practicesInstallation and upgradeOperationInitial configurationConfiguration managementConfig environmentsIn the Config EditorExamplesConfiguration variablesConfiguration contextsPlanning configuration contextsConfiguration and usageBest practicesRecommended use casesNon-recommended use casesConfig contexts vs. IAM instancesExternal configuration secretsStoring values with Config EditorStoring values using CLIKeystore toolsTechnical informationIAM Config Editor (UI)Plugin treesPlugin overviewPlugin propertiesFlow step plugins in IAM flowsSensitive config valuesView togglesConfiguration validationLoading/saving configurationsConfiguration activation timeoutConfiguration activation internalsModule filenamesExamples of activation state filesCommand-Line InterfaceAuthenticationSelf-servicesTarget applicationsOIDC and OAuthSAMLAPI access controlFlows (Airlock IAM concept)Loginapp (module)Adminapp (module)Service Container (module)Transaction approval (module)IAM REST APIsCustomizing UIs and textsThird-party licensesConfiguration managementConfiguration managementThe configuration is managed using the Config Editor. See IAM Config Editor (UI).Chapter contentConfiguration environmentsUsing environment variables in the IAM configurationConfiguration contextsStoring sensitive configuration values externallyIAM Config Editor (UI)IAM Command-Line Interface (CLI)
Chapter contentConfiguration environmentsUsing environment variables in the IAM configurationConfiguration contextsStoring sensitive configuration values externallyIAM Config Editor (UI)IAM Command-Line Interface (CLI)