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
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -288,13 +288,14 @@ Follow the guides below to configure each part.
288
288
</summary>
289
289
290
290
291
-
First you must configure your JFrog instance to have an OpenID Connect integration to your Azure DevOps server.
292
-
Login to your JFrog instance as an Administrator, then as [described in the documentation:](https://jfrog.com/help/r/jfrog-platform-administration-documentation/openid-connect-configurations-overview)
291
+
First, configure an OpenID Connect integration to your Azure DevOps server in your JFrog instance.
292
+
Log in to your JFrog instance as an administrator,
293
+
then as [described in the documentation:](https://jfrog.com/help/r/jfrog-platform-administration-documentation/openid-connect-configurations-overview)
293
294
294
-
1. Go to the Administrator panel.
295
-
2. Select General Management.
296
-
3. Choose Manage Integrations.
297
-
4. Select New Integration - OpenID Connect
295
+
1. Go to the **Administrator panel**.
296
+
2. Select **General Management**.
297
+
3. Choose **Manage Integrations**.
298
+
4. Select New Integration - **OpenID Connect**
298
299
299
300
Now fill out the integration with the parameters of your Azure DevOps instance.
300
301
@@ -307,13 +308,13 @@ Now fill out the integration with the parameters of your Azure DevOps instance.
In order to obtain your Azure DevOps Organization GUID (`{ORG_GUID}`) you can simply run a pipeline in your Azure DevOps organization using any of the JFrog Task setup using a Service Connection configured with the `OpenID Connect Integration` authentication method, see the [Configure the Service Connection](#configure-the-service-connection) section. Even if the task fails due to you not yet having configured the Integration in JFrog, it will output the relevant information as part of the pipeline.
315
316
316
-
In the Pipeline Output, look for the `OIDC Token Issuer`, this value is what you must put in as your `Provider URL`.
317
+
In the Pipeline Output, look for the `OIDC Token Issuer`,value, which you need to enter as your `Provider URL`.
317
318
The rest of the information can also be helpful for you to configure the Identity Mappings as described in the section below.
318
319
319
320
```
@@ -376,7 +377,6 @@ Just make sure to never replace your Organization name with a `*` operator as th
376
377
</summary>
377
378
378
379
You must configure a `ServiceConnection` setting the `Authentication method` to `OpenID Connect Integration`.
379
-
All four types of Service Connections are supported, they will all require the same input regardless of the type.
380
380
381
381
This requires you to fill in the following inputs:
0 commit comments