Skip to content

Commit

Permalink
C Dawes changes
Browse files Browse the repository at this point in the history
  • Loading branch information
davidsayer57 committed Mar 4, 2024
1 parent 49968af commit fe8d90e
Show file tree
Hide file tree
Showing 5 changed files with 224 additions and 224 deletions.
12 changes: 6 additions & 6 deletions 9.3.5/helm_oidc_config.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# Configuring Leap with OIDC {#helm_oidc_config .concept}
# Configuring Leap with OIDC

This topic describes how to configure an HCL Leap server that was deployed using Helm with an OpenID Connect identity provider.

Expand Down Expand Up @@ -84,21 +84,21 @@ For more details on defining a server customization, see [helm\_open\_liberty\_c

The following properties must be set to complete the OIDC configuration:

- hasUserLookups - By setting this to false it will disable user lookups, which is not available when configured with OIDC.
- hasUserGroups - By setting this to false it will disable group lookups, which is not available when configured with OIDC.
- userLookups - By setting this to false it will disable user lookups, which is not available when configured with OIDC.
- userGroups - By setting this to false it will disable group lookups, which is not available when configured with OIDC.
- postLogoutRedirectURL - This is the URL to which Leap will redirect the browser after a user chooses to log out. This is necessary to complete the loop with the OIDC IDP.

``` {#codeblock_hbq_pnt_b1c}
configuration:
leap:
leapProperties: |
ibm.nitro.NitroConfig.hasUserLookup=false
ibm.nitro.NitroConfig.hasUserGroups=false
ibm.nitro.NitroConfig.userLookup=false
ibm.nitro.NitroConfig.userGroups=false
ibm.nitro.LogoutServlet.postLogoutRedirectURL=https://myOIDCServer.com/realms/Leap/protocol/openid-
connect/logout?client_id=hcl-leap-oidc-client&post_logout_redirect_uri=https://myLeapServer.com/apps/secure/org/ide/manager.html
```

For more details on setting Leap properties, see [helm\_leap\_properties.md](helm_leap_properties.md).
For more details on setting Leap properties, see [Leap properties](helm\_leap\_properties.md).

## Restart the pod {#section_zq2_vmt_b1c .section}

Expand Down
14 changes: 7 additions & 7 deletions docs/9.3.5/helm_oidc_config.html
Original file line number Diff line number Diff line change
Expand Up @@ -102,7 +102,7 @@
<div data-md-component="skip">


<a href="#helm_oidc_config" class="md-skip">
<a href="#configuring-leap-with-oidc" class="md-skip">
Skip to content
</a>

Expand Down Expand Up @@ -7018,7 +7018,7 @@



<h1 class="concept" id="helm_oidc_config">Configuring Leap with OIDC</h1>
<h1 id="configuring-leap-with-oidc">Configuring Leap with OIDC</h1>
<p>This topic describes how to configure an HCL Leap server that was deployed using Helm with an OpenID Connect identity provider.</p>
<h2 class="section" id="section_lmm_5mt_b1c">Configuring Leap with OIDC</h2>
<p>Leap can be configured to leverage OpenID Connect (OIDC) as the primary authentication mechanism. This means that Leap will be turned into a Relying Party (RP) to the specified identify provider (IDP). When OIDC is used, the user and group lookup feature of Leap is not available and must be disabled as part of the configuration.</p>
Expand Down Expand Up @@ -7081,19 +7081,19 @@ <h2 class="section" id="section_vxv_fnt_b1c">Add OIDC definition as a server cus
<h2 class="section" id="section_r3z_knt_b1c">Add config properties related to OIDC config</h2>
<p>The following properties must be set to complete the OIDC configuration:</p>
<ul>
<li>hasUserLookups - By setting this to false it will disable user lookups, which is not available when configured with OIDC.</li>
<li>hasUserGroups - By setting this to false it will disable group lookups, which is not available when configured with OIDC.</li>
<li>userLookups - By setting this to false it will disable user lookups, which is not available when configured with OIDC.</li>
<li>userGroups - By setting this to false it will disable group lookups, which is not available when configured with OIDC.</li>
<li>postLogoutRedirectURL - This is the URL to which Leap will redirect the browser after a user chooses to log out. This is necessary to complete the loop with the OIDC IDP.</li>
</ul>
<div id="codeblock_hbq_pnt_b1c" class="highlight"><pre><span></span><code>configuration:
leap:
leapProperties: |
ibm.nitro.NitroConfig.hasUserLookup=false
ibm.nitro.NitroConfig.hasUserGroups=false
ibm.nitro.NitroConfig.userLookup=false
ibm.nitro.NitroConfig.userGroups=false
ibm.nitro.LogoutServlet.postLogoutRedirectURL=https://myOIDCServer.com/realms/Leap/protocol/openid-
connect/logout?client_id=hcl-leap-oidc-client&amp;post_logout_redirect_uri=https://myLeapServer.com/apps/secure/org/ide/manager.html
</code></pre></div>
<p>For more details on setting Leap properties, see <a href="helm_leap_properties.html">helm_leap_properties.md</a>.</p>
<p>For more details on setting Leap properties, see <a href="helm_leap_properties.html">Leap properties</a>.</p>
<h2 class="section" id="section_zq2_vmt_b1c">Restart the pod</h2>
<p>After restarting the Leap pod, accessing Leap should redirect you to authenticate using your OIDC IDP.</p>

Expand Down
2 changes: 1 addition & 1 deletion docs/9.3.5/search/search_index.json

Large diffs are not rendered by default.

Loading

0 comments on commit fe8d90e

Please sign in to comment.