Estimated reading time:
You are browsing documentation for an outdated version of Kong. Go here
to browse the documentation for the latest version.
Table of Contents
In this section you will learn how to manage Kong Admins in the Kong Admin GUI.
- You have enabled authentication, following the Getting Started guide.
- You have enabled RBAC
- You have setup the Super Admin RBAC Role or you are able to login with a user that has
/rbac read/write access, with all associated endpoints for permission creation. We will refer to this user as the Authorized Admin in this guide.
Create RBAC Roles for Your Admin
For every Admin that is using the Kong Admin GUI, they will need roles assigned to them based on which resources they can access.
Login as the Authorized Admin and click “Admins” in the sidebar. Next, click “Add Role”. Fill out the form, and add the endpoint permissions. Name the role accordingly (e.g. “read-only”, “read-services”).
⚠️ IMPORTANT: Every Admin that needs access to the Admin GUI will need at least
read access to the home “
Create an Admin
Login to the Kong Admin GUI as the Super Admin. Click “Admins” in the sidebar. Click “Add Admin”. Fill out the form with a username and associated Role.
Grant Admin Access
Now that you have created an Admin and assigned them roles, you will need to give them access to login to the Admin GUI. If not using the LDAP Auth Advanced plugin, you will need to create Credentials via the API, as it is not currently supported in the Admin GUI.
If you are using LDAP Auth Advanced Plugin, then you can skip credential creation and utilize the Consumer mapping feature, which allows you to map a LDAP user’s
username to a consumer’s
Admins are a type of Kong Consumer, and therefore can be given Kong Plugin Authentication Credentials. Find the value of your Kong configuration directive
admin_gui_auth. You will need to create credentials based on that plugin. Ensure that you have the Admin entity data:
$ curl 'http://kong:8001/admins/<username>'
HTTP/1.1 200 OK
"comment": "User generated on creation of Admin.",
Now that you have the
<CONSUMER_ID>, you can use this to create a credential with your associated
Once a user has a credential, they can use the credential to log in.
Next: Networking ›