Previous Next JavaScript must be enabled to correctly display this content

## 8 Configuring Different URL’s on the Basis of Enterprise Roles

To enable URL separation based on enterprise roles using custom header name and value, the following queries needs to be executed in `DIGX_FW_CONFIG_ALL_B` table

    Insert into DIGX_FW_CONFIG_ALL_B
    (PROP_ID, CATEGORY_ID, PROP_VALUE,FACTORY_SHIPPED_FLAG,
    PROP_COMMENTS, SUMMARY_TEXT, CREATED_BY, CREATION_DATE,LAST_UPDATED_BY,

    LAST_UPDATED_DATE, OBJECT_STATUS, OBJECT_VERSION_NUMBER)

    values ('IS_LOGIN_SEPARATION_ENABLED','SecurityConstants','true','N',null,
    'Is login separation enabled','ofssuser',sysdate,'ofssuser',sysdate,'Y',1);

This query enables the URL separation mechanism. By default the URL separation mechanism is not enabled.

    Insert into DIGX_FW_CONFIG_ALL_B (PROP_ID, CATEGORY_ID, PROP_VALUE,
    FACTORY_SHIPPED_FLAG, PROP_COMMENTS, SUMMARY_TEXT, CREATED_BY, CREATION_DATE,

    LAST_UPDATED_BY, LAST_UPDATED_DATE, OBJECT_STATUS, OBJECT_VERSION_NUMBER)

    values ('LOGIN_HEADER_NAME','SecurityConstants',<HEADER_NAME>,'Y',null,
    'Header name for login separation','ofssuser',sysdate,'ofssuser',sysdate,'Y',1);

This query is used to provide entry for the custom header name.

    Insert into DIGX_FW_CONFIG_ALL_B (PROP_ID, CATEGORY_ID, PROP_VALUE,
    FACTORY_SHIPPED_FLAG, PROP_COMMENTS, SUMMARY_TEXT, CREATED_BY, CREATION_DATE,

    LAST_UPDATED_BY, LAST_UPDATED_DATE, OBJECT_STATUS, OBJECT_VERSION_NUMBER)

    values (<HEADER_NAME>,'SecurityConstants',<HEADER_VALUE>,'Y',null,'login separation header name
    and value pair','ofssuser',sysdate,'ofssuser',sysdate,'Y',1);

This query is used for mapping the custom header name with its corresponding value.

    Insert into DIGX_FW_CONFIG_ALL_B (PROP_ID, CATEGORY_ID, PROP_VALUE,
    FACTORY_SHIPPED_FLAG, PROP_COMMENTS, SUMMARY_TEXT, CREATED_BY, CREATION_DATE,

    LAST_UPDATED_BY, LAST_UPDATED_DATE, OBJECT_STATUS, OBJECT_VERSION_NUMBER)

    values (<HEADER_VALUE>,'SecurityConstants',<ENTERPRISE_ROLE>,'Y',null,
    'Enables login separation for given enterprise role','ofssuser',sysdate,'ofssuser',sysdate,'Y',1);

This query is used for mapping the custom header value with the enterprise role for which the URL separation has be to achieve.

In the above queries, `<HEADER_NAME>` field denotes the custom header name, `<HEADER_VALUE>` denotes the custom header value, and `<ENTERPRISE_ROLE>` field denotes the enterprise role. These fields need to be replaced with own custom values before executing the queries.

OHS Configuration:

To support it OHS need to send an additional header to Weblogic server. To enable this Implementer need to configure a new port and create a virtual host where that custom header is added in the request.

Sample snippet is below

    Listen PORT_NO<VirtualHost *:PORT_NO >
    RequestHeader add <HEADER_NAME> "<HEADER_VALUE> "
    <Location /digx>
    SetHandler weblogic-handler
    WebLogicCluster WEBLOGIC_HOST:WEBLOGIC_PORT
    </Location>
    </VirtualHost>