Skip to content

Commit 1173138

Browse files
committed
Update README.md
1 parent bfbe0d2 commit 1173138

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

README.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -288,13 +288,14 @@ Follow the guides below to configure each part.
288288
</summary>
289289

290290

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)
293294

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**
298299

299300
Now fill out the integration with the parameters of your Azure DevOps instance.
300301

@@ -307,13 +308,13 @@ Now fill out the integration with the parameters of your Azure DevOps instance.
307308
| Audience | example: `api://AzureADTokenExchange` |
308309
| Token Issuer | If the issuer is different from the provider, for Azure DevOps this can be left blank. |
309310

310-
As an example the final integration configuration will look like:
311+
For example, the final integration configuration will look like this:
311312

312313
![oidc-integration.png](images/oidc-integration.png)
313314

314315
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.
315316

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`.
317318
The rest of the information can also be helpful for you to configure the Identity Mappings as described in the section below.
318319

319320
```
@@ -376,7 +377,6 @@ Just make sure to never replace your Organization name with a `*` operator as th
376377
</summary>
377378

378379
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.
380380

381381
This requires you to fill in the following inputs:
382382

0 commit comments

Comments
 (0)