Conditions of use -c junctions

Use the -c junction option to insert information into HTTP headers of requests. Separate multiple arguments to the -c option with commas only. Do not enter any spaces. The -c all option passes the following headers only...

• iv-user (HTTP_IV_USER)
• iv-groups (HTTP_IV_GROUPS)
• iv-creds (HTTP_IV_CREDS)

The -c all option does not pass iv-user-l (HTTP_IV_USER_L)) headers.

The HTTP_IV_USER header is used for either iv-user and iv-user-l when only one of them is specified. If both iv-user and iv-user-l headers are specified, HTTP_IV_USER_L is used for iv-user-l. To ensure security of the iv-creds header value, use SSL junctions. The content caching mechanism does not cache responses to requests over junctions configured with the -c and -C options. We can improve the WebSEAL performance under -c junction conditions by applying the cache configuration.

To pass all four header types across the junction, individually specify all four header options

-c iv_user,iv_user_l,iv_groups,iv_creds

Pass iv-user-l (HTTP_IV_USER) header to back-end appserver.

-c iv_user_l

Pass iv-user (HTTP_IV_USER), iv-groups (HTTP_IV_GROUPS), and iv-creds (HTTP_IV_CREDS) headers to back-end appserver.

-c all

Pass iv-user (HTTP_IV_USER), iv-user-l (HTTP_IV_USER_L), iv-groups (HTTP_IV_GROUPS), and iv-creds (HTTP_IV_CREDS) headers to back-end appserver.

-c iv_user,iv_user_l,iv_groups,iv_creds

Parent topic: Single Sign-on Solutions