About application attribute data stores
Application attributes come from a variety of data stores or sources. The most common source is your Okta Tenant, however other data store types are supported as well, for example Database and LDAPLightweight Directory Access Protocol (LDAP) is a lightweight client-server protocol for accessing directory services, specifically X.500-based directory services. LDAP runs over TCP/IP or other connection oriented transfer services..
The Data Source field defines the source for the value of the attribute. The following data sources are available:
|IDPAn acronym for Identity Provider. It is a service that manages end user accounts analogous to user directories such as LDAP and Active Directory, and can send SAML responses to SPs to authenticate end users. Within this scenario, the IdP is Okta.||The value of the is populated from the IDP field selected in the Value field. This is your Okta Tenant|
|Static||The value of the attribute is fixed and defined in the Value field|
|Secret||The value of the attribute is a static protected value, used as a secret key by the application in order to trust the headers that originate from the Access Gateway.|
The value of the attribute comes from the OID datasource. The OID Datasouce is available in the Oracle E-Business Suite and other application types which provide LDAP support. Typically used to to retrieve the Oracle GUID.
|Auth Context||The value of the attribute comes from the authentication context which includes the remote address and session id|
|AppAn abbreviation of application. Essentially, it is a web-based site used to perform any number of specific tasks, and requires authentication from end users by signing in. Context||The value of the attribute comes from the application context and includes such fields as domainA domain is an attribute of an Okta organization. Okta uses a fully-qualified domain name, meaning it always includes the top-level domain (.com, .eu, etc.), but does not include the protocol (https)., cookie domain,|