Manage application attributes
To manage application attributes:
- Navigate to the Access Gateway Admin UI console.
- From the Topology tab or the Applications tab, open the application.
- Select the Attributes pane.
The list of known attributes for the application displays and is similar to:
. . .
- From the available set of attributes, select any one of the following options:
Add a new attribute Delete an existing attribute Modify an existing attribute Test an attribute set
Add a new attribute
- Click Add () in the attribute list header.
The new Attribute dialog box appears. You may need to scroll to the display as new attributes are added at the end of the page.
- From the Data Source drop-down box, select an appropriate data source.
See Data Source Types for a list of supported data source types and their meaning.
- From the Field drop-down box, select a field name. This is the source of the content for the header element.
- From the Type drop-down box, select the appropriate target type, either Header or Cookie.
- In the Name field, enter the name for the header or cookie value expected by the legacy application.
For example, to map the IDP field username to the header field login, you need to create an attribute resembling:
- Click Okay when the attribute is complete.
Delete an existing attribute
- Click Delete () associated with the attribute you want to delete.
- In the confirm dialog box, click Yes to delete the attribute or No to cancel the delete operation.
Modify an existing attribute
- Click Edit () associated with the attribute you want to modify. The Edit existing attribute dialog box appears.
- Modify the attribute as required.
- Click Okay to save the modified attribute or Cancel to cancel the modification.
Test an attribute set
- Click Test () in the attribute list header. The simulator dialog box appears.
- Enter a value for a field that you want to test.
- Click Test.
- Examine the result. You may need to scroll the simulator window at the end of the page to see the test results.
- Modify a value and re-run the test or click Close to close the simulator dialog box.
Application attributes are composed of the following elements:
Controls whether an attribute is present or not present within a header or cookie.
Attributes used for policy decisions are typically set to Don't Send.
The source of origin for the contents of the attribute. It can be any of a number of sources including IDP, various contexts, Data Stores, and others.
Field and Record Number
Either Field and Record Number, or Value.
For static and secret attributes, the Value field represents a fixed value for the attribute.
For non-static fields, Field field is used as the source for the attribute.
Record Number is only present with non-static fields and represents which of a multi-value variable will be selected. Record Value can be one of the following:
Maximum length: 128 characters.
Method for passing attributes. The type can be one of the following:
Associated field in either the header or cookie.
Data source types
The Data Source field defines the source for the value of the attribute. The following data sources are available:
|IDP||The value of the attribute 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. It is used as a secret key by the application to trust the headers, which originate from Access Gateway.|
The value of the attribute comes from the OID data source. The OID data source is available in the Oracle E-Business Suite and other application types that provide LDAP support. You can use it 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.|
|App Context||The value of the attribute comes from the application context and includes fields, such as domain, cookie domain, and so on.|