IBM Verify

IBM Verify

Join this online user group to communicate across Security product users and IBM experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Back to discussions
Expand all | Collapse all

Automating Exporting Importing/Updating junction config.

  • 1.  Automating Exporting Importing/Updating junction config.

    Posted 05/04/20 07:48 AM
    Hi,

    If you export/call the endpoint 

    https://{appliance_hostname}/wga/reverseproxy/{reverseproxy_id}/junctions?junctions_id={junctions_id}

    You get a response that look like this.
    {
    "junction_point":"/test",
    "description":"Test application point of contact",
    "active_worker_threads":"0",
    "authz_rules":"no",
    "basic_auth_mode":"filter",
    "boolean_rule_header":"no",
    "client_ip_http":"do not insert",
    "cookie_include_path":"no",
    "delegation_support":"no",
    "forms_based_sso":"disabled",
    "fsso_config_file":"disabled",
    "http_header_ident":"insert - iv_user iv_user_l iv_groups iv_creds",
    "insert_session_cookies":"no",
    "junction_hard_limit":"0 - using global value",
    "junction_soft_limit":"0 - using global value"
    "junction_type":"SSL",
    "mutual_auth":"no",
    "preserve_cookie":"no",
    "remote_http_header":"insert - iv_user iv_user_l iv_groups iv_creds",
    "request_encoding":"UTF-8, URI Encoded",
    "scripting_support":"no",
    "session_cookie_backend_portal":"no",
    "stateful_junction":"no",
    "tfim_sso":"no",
    "transparent_path_junction":"no",
    "servers":"server_uuid!e841e652-82c2-11e2-8670-000c29f1e7c2;server_state!running;operation_state!Online;server_hostname!w3.ibm.com;server_port!80;http_port!80;virtual_junction_hostname!w3.ibm.com;server_dn!;local_ip!;query_content_url!/cgi-bin/query_contents;query_contents!unknown;case_sensitive_url!no;windows_style_url!yes;current_requests!0;total_requests!1;"
    }

    If you want to import that config you just exported it is not possible because the api for creating a junction is a bit different. For example the servers part. Why do we get runtime information together with config

    https://{appliance_hostname}/wga/reverseproxy/{reverseproxy_id}/junctions


    Will this be fixed in the next release? Or are the any other way around it without coding to much.

    ------------------------------
    Regards Mikael
    ------------------------------


Related Content