You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+23-17Lines changed: 23 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -274,6 +274,10 @@ Setting up OpenID Connect has 3 separate parts:
274
274
- Configuring Identity Mappings with Claim rules, matching to Projects & Service Connections.
275
275
- Configuring Service Connections as OpenID Connect in the Projects in your Azure Devops Instance.
276
276
277
+
> [!IMPORTANT]
278
+
> To use OIDC authentication, make sure you're using **JFrog CLI version 2.75.0 or later**
279
+
> and **JFrog Azure DevOps Extension version 2.11.0 or later**.
280
+
277
281
Follow the guides below to configure each part.
278
282
279
283
<details>
@@ -385,29 +389,31 @@ This requires you to fill in the following inputs:
385
389
| Description (optional) | A short of the purpose of this ServiceConnection |
386
390
387
391
388
-
> **Tip**: When using JFrog CLI version `2.75.0` or later, the extension automatically exports the authenticated user and access token
392
+
> [!TIP]
393
+
> When using JFrog CLI version `2.75.0` or later, the extension automatically exports the authenticated user and access token
389
394
> as step outputs named `oidc_user` and `oidc_token`. These outputs can be used in later steps (e.g., for Docker login, Helm registry, or custom scripts).
390
395
>
396
+
> If you override the CLI version in your pipeline and use an older version, these outputs may not be available.
0 commit comments