Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit959a896

Browse files
authored
Sso okta updates (#681)
* Update saml-okta.md* Update saml-okta.md* Update saml-okta.md* Update saml-okta.md* Update saml-okta.mdRestored new auto sync and activate fields for okta* Update saml-okta.mdAdded app ID field to codefresh settings* Update variables.mdRemoved comment tags from cf_export encryption content* Update variables.md
1 parent3a5ca72 commit959a896

File tree

2 files changed

+17
-5
lines changed

2 files changed

+17
-5
lines changed

‎_docs/pipelines/variables.md‎

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -269,12 +269,11 @@ cf_export MY_VAR # Correct syntax
269269
```
270270

271271

272-
<br>
273272

274273
####Masking variables within`cf_export`
275274

276275
Mask variables within`cf_export` by defining the`--mask` flag.
277-
Values of masked variables in`cf_export` commands are replaced with asterisks in theBuild variable list. This helps to ensure that sensitive information is not exposed also in the variables list, in addition to the logs.
276+
Values of masked variables in`cf_export` commands are replaced with asterisks in thebuild logs. This helps to ensure that sensitive information is not exposed also in the variables list, in addition to the logs.
278277

279278
Here is an example with standard and masked versions of the same variable in`cf_export` commands.
280279

@@ -295,8 +294,6 @@ steps:
295294

296295

297296

298-
<br>
299-
300297

301298
####Export variables to all steps with`cf_export`
302299

‎_docs/single-sign-on/saml/saml-okta.md‎

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,14 +19,29 @@ Setting up SAML SSO for Okta includes:
1919
##Step 1: Configure SSO settings for Okta via SAML in Codefresh
2020
Create a SAML account for Okta in Codefresh to create an integration for Codefresh in Okta.
2121

22+
23+
SAML SSO settings for Okta include auto-syncing teams and groups in OKta with Codefresh, and automatically activating new users synced to Codefresh.
24+
25+
<b>TIP</b>:
26+
>Use the auto-sync and activate user options for Just in Time (JIT) Provisioning.
27+
2228
1. In the Codefresh UI, from the toolbar click the**Settings** icon.
2329
1. In the sidebar, from Access & Collaboration, select[Single Sign-On](https://g.codefresh.io/2.0/account-settings/single-sign-on){:target="\_blank"}.
2430
1. Click**Add single-sign-on**, select**SAML**, and then click**Next**.
2531
1. Enter the connection details:
2632
***Display Name**: Any name you want for the integration.
2733
***IDP Entry**: Type in any character. You will enter the correct value from Okta in the final step.
2834
***Application Certificate**: You will enter the correct value from Okta in the final step.
29-
***Provider**: Leave empty.
35+
***Provider**: Select**Okta**.
36+
***Auto-sync users and teams to Codefresh**: Optional. When selected, automatically syncs teams or groups in Okta to Codefresh, every 12 hours by default. You can define a different sync interval in**Sync interval**.
37+
>**NOTE**:
38+
>Though you can assign an Okta application to both groups and individual users, Codefresh_only syncs users who are part of teams_.
39+
New users in Okta, _not_ assigned to a team, are **NOT** synced with Codefresh. You should first assign the user to a team for the sync to work.
40+
***Activate user after sync**: Optional. When selected, Codefresh automatically invites and activates new users added during the automated sync, without waiting for the users to accept the invitations.
41+
***Access Token**: Optional. The OKTA API token that you generated in Okta, used to sync groups and their users from OKTA to Codefresh.
42+
***Client Host**: The OKTA organization URL, for example,`https://<company>.okta.com`.
43+
***Application ID**: The Codefresh application ID in your OKTA organization, that will be used to sync groups and user from OKTA to Codefresh.
44+
3045
1. Click**Add**.
3146
The SAML integration for Okta is added and appears in the list of SSOs.
3247
1. In the Single Sign-On page, click the**Edit** icon for the Okta SAML integration you created.

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp