The general idea is to have user groups defined in the Okta, and Okta has to pass a user’s group when he will log in to the Jenkins.
Then Jenkins has to assign correct permissions for this user based on its group(s).
global roles
: obviously, global roles for global permissions, such as create/delete Views, Jobs, Overall
project roles
: the permission settings on a per-project basis – jobs are limited by a regular expression
agent roles
: Jenkins slaves/workers/agent permissions
If you’ll try to log in right now – will face with the “
missing the Overall/Read permission
” error:
To avoid it – we need to create a global role with the
Overall Read
permissions.
Go to the
Manage Roles
:
Create a new global role called
read_all
and set permissions to the
Overall – Read
:
Save.
Could you please present a demo spring boot app to authenticate user with okta using SAML protocol.
Could you please show how to use spring's "SAMLAuthenticationProvider"
How Can I Create a DevOps Pipeline That Automatically Resolves All Conflicts and Bugs Without Human Intervention?
