Skip to content

RHIDP-9758: Enable GitLab authentication#1798

Closed
deerskindoll wants to merge 19 commits intoredhat-developer:mainfrom
deerskindoll:RHIDP-9758
Closed

RHIDP-9758: Enable GitLab authentication#1798
deerskindoll wants to merge 19 commits intoredhat-developer:mainfrom
deerskindoll:RHIDP-9758

Conversation

@deerskindoll
Copy link
Member

IMPORTANT: Do Not Merge - To be merged by Docs Team Only

Version(s):

main, 1.9

Issue:

https://issues.redhat.com/browse/RHIDP-9758

Preview:

The basic configuration in {product-very-short} requires only a few simple steps.

.Prerequisites
* You have configured link:https://docs.gitlab.com/api/oauth2/[GitLab OAuth application].
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With:

  • Call back URL = ???
  • Permissions = ???

* You have set up link:https://docs.gitlab.com/user/profile/personal_access_tokens/[GitLab personal access tokens].
* You have set up a link:https://docs.gitlab.com/user/group/[GitLab parent group].

.Procedure
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Step 1: Create the Gitlab OAuth application with required parameters: callback URL + permissions.

Step 2: Create OpenShift secrets with the Gitlab related stuff: GITLAB_HOST, GITLAB_CLIENT_ID, GITLAB_CLIENT_SECRET,GITLAB_PARENT_ORG

* You have set up a link:https://docs.gitlab.com/user/group/[GitLab parent group].

.Procedure
. Enable the `backstage-plugin-catalog-backend-module-gitlab-org-dynamic` plugin.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • snippet explaining as in other authentication procedures

Comment on lines +56 to +61
integrations:
gitlab:
- host: ${GITLAB_HOST}
token: ${GITLAB_TOKEN}
apiBaseUrl: https://${GITLAB_HOST}/api/v4
----
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider moving it to the integration title.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(with the additional steps: create a PAT in GitLab, Create the Openshift secrets containing the PAT)

Enter `production` to disable the Guest login option in the {product-short} login page.

`audience`::
Enter your GitLab instance address: `https://${GITLAB_HOST}`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Enter your GitLab instance address: `https://${GITLAB_HOST}`.
Enter your GitLab instance address: pass:c,a,q[`https://${GITLAB_HOST}`].

@rhdh-bot
Copy link
Collaborator

rhdh-bot commented Feb 17, 2026

Copy link
Member

@albarbaro albarbaro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nothing wrong with the content itself, but I agree with Fabrice that it can be structured differently: his suggestions make perfect sense.
The moving parts (authentication, ingestion, gitlab app, integration) are mostly the same as Github, so using that same content structure we have for Github would make it more clear.
Details and permissions for the Gitlab App and Token should be in the notes doc attached to the Jira Feature, but if it's not enough or I missed something let me know and I can provide more.

@deerskindoll
Copy link
Member Author

@themr0c @albarbaro thank you both! content updated according to your feedback, please take a look

@sonarqubecloud
Copy link

@deerskindoll
Copy link
Member Author

/cherry-pick release-1.9

@openshift-cherrypick-robot
Copy link
Contributor

@deerskindoll: once the present PR merges, I will cherry-pick it on top of release-1.9 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-1.9

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@pabel-rh
Copy link
Member

Created #1839 to make updates in Jana's absence. Hence, closing this PR for now.

@pabel-rh pabel-rh closed this Feb 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Technical review needed 🔩 Test all the procedures

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants