Skip to content

Repo sync #39607

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.

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

Merged
merged 3 commits into from
Aug 1, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,8 @@ In your {% data variables.product.prodname_actions %} workflow file, ensure you

The following example uses the placeholders `YOUR_PROVIDER_NAME` and `YOUR_AUDIENCE`.

{% raw %}

```yaml
permissions:
id-token: write
Expand All @@ -77,13 +79,17 @@ jobs:

```

{% endraw %}

> [!TIP]
> When OIDC authentication is used, the `setup-jfrog-cli` action automatically provides `oidc-user` and `oidc-token` as step outputs.
> These can be used for other integrations that require authentication with JFrog.
> To reference these outputs, ensure the step has an explicit `id` defined (for example `id: setup-jfrog-cli`).

### Using OIDC Credentials in other steps

{% raw %}

```yaml
- name: Sign in to Artifactory Docker registry
uses: docker/login-action@v3
Expand All @@ -93,6 +99,8 @@ jobs:
password: ${{ steps.setup-jfrog-cli.outputs.oidc-token }}
```

{% endraw %}

## Further reading

* [OpenID Connect Integration](https://jfrog.com/help/r/jfrog-platform-administration-documentation/openid-connect-integration) in the JFrog documentation
Expand Down
2 changes: 2 additions & 0 deletions data/reusables/organizations/additional-permissions.md
Original file line number Diff line number Diff line change
Expand Up @@ -59,10 +59,12 @@ For more information, see [AUTOTITLE](/discussions).
* View {% data variables.product.prodname_secret_scanning %} results
* Dismiss or reopen {% data variables.product.prodname_secret_scanning %} results

{%- ifversion ghec %}
### Actions

* Manage {% data variables.product.prodname_actions %} general settings
* Manage runners
* Manage secrets
* Manage variables
* Manage environments (including environment secrets and variables)
{%- endif %}
2 changes: 1 addition & 1 deletion data/reusables/repositories/rulesets-bypass-step.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ You can grant certain roles, teams, or apps bypass permissions {% ifversion push

* Repository admins, organization owners, and enterprise owners
* The maintain or write role, or custom repository roles based on the write role
* Teams
* Teams, excluding secret teams. See [AUTOTITLE](/organizations/organizing-members-into-teams/about-teams#team-visibility).
{%- ifversion ghes %}
* Deploy keys
{%- endif %}
Expand Down
Loading