Skip to content

DBACLD-160975 [ODM K8S] Validate Instructions for using OKTA Provider… #223

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: vnext-release
Choose a base branch
from
Open

DBACLD-160975 [ODM K8S] Validate Instructions for using OKTA Provider… #223

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8dec6c0
DBACLD-160975 [ODM K8S] Validate Instructions for using OKTA Provider…
lgrateau Apr 30, 2025
c2da984
Try to fix link checker
lgrateau Apr 30, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions .md_check_config.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,8 @@
{
"ignorePatterns": [
{
"pattern": "^http://localhost"
"pattern": "^http://localhost",
"pattern": "^https://jwt.io"
}
],
"replacementPatterns": [
Expand All @@ -11,4 +12,4 @@
}
],
"timeout": "20s"
}
}
8 changes: 4 additions & 4 deletions authentication/Okta/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -288,10 +288,10 @@ In this step, we augment the token with meta-information that is required by the
```

Where:
- *OKTA_API_SCOPE* has been defined [above](#configure-the-default-authorization-server) (*odmapiusers*)
- *OKTA_SERVER_NAME* has been obtained from [previous step](#retrieve-okta-server-information)
- Both *OKTA_CLIENT_ID* and *OKTA_CLIENT_SECRET* are listed in your ODM Application, section **Applications** / **Applications** / **ODM Application** / **General** / **Client Credentials**
- *OKTA_SERVER_NAME* has been obtained from [previous step](#retrieve-okta-server-information)
- *OKTA_ODM_GROUP* is the ODM Admin group we created in a [previous step](#manage-group-and-user) (*odm-admin*)
- *OKTA_API_SCOPE* has been defined [above](#configure-the-default-authorization-server) (*odmapiusers*)

The files are generated into the `output` directory.

Expand Down Expand Up @@ -321,15 +321,15 @@ In this step, we augment the token with meta-information that is required by the
```
```
NAME CHART VERSION APP VERSION DESCRIPTION
ibm-helm/ibm-odm-prod 24.1.0 9.0.0.1 IBM Operational Decision Manager
ibm-helm/ibm-odm-prod 25.0.0 9.5.0.0 IBM Operational Decision Manager
```

3. Run the `helm install` command.

You can now install the product. We will use the PostgreSQL internal database and disable the data persistence (`internalDatabase.persistence.enabled=false`) to avoid any platform complexity concerning persistent volume allocation.

```
helm install my-odm-release ibm-helm/ibm-odm-prod --version 24.1.0 \
helm install my-odm-release ibm-helm/ibm-odm-prod --version 25.0.0 \
--set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=icregistry-secret \
--set oidc.enabled=true \
--set internalDatabase.persistence.enabled=false \
Expand Down