Skip to content
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.

Sign up for GitHub

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

Warning about multiples kubeconfig with the same user #737

Merged
merged 5 commits into from
Mar 16, 2020
Merged

Warning about multiples kubeconfig with the same user #737

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
ad1ef23
Warning about multiples kubeconfig with the same user
jvanz Mar 10, 2020
f53b183
Make this a separate section and add a couple of langauge edits.
nkoranova Mar 11, 2020
e1eaea4
Workaround about issue of using the same user in multiples kubeconfig
jvanz Mar 13, 2020
03d75a2
Minor style edit.
nkoranova Mar 16, 2020
a986885
Additional sentence about the users section and the oidc tokens.
nkoranova Mar 16, 2020
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
28 changes: 28 additions & 0 deletions adoc/admin-security-rbac.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,6 +163,34 @@ NOTE: Before any add-on upgrade, please backup any runtime configuration changes
login username and password.
. The kubeconfig `kubeconf.txt` is generated locally.

===== OIDC Tokens

The kubeconfig file (`kubeconf.txt`) contains the OIDC tokens necessary to perform authentication and authorization in the cluster.
OIDC tokens have an *expiration date* which means that they need to be refreshed after some time.
If you use the *same user in multiples kubeconfig files* distributed among multiple machines,
this can lead to issues, because only one of the machines will be able to refresh the token.
The user will be able to download multiple kubeconfig files, but they will only work until one of them needs to refresh the session.
After that, only one machine will work, namely the first machine which refreshed the token.

*A workaround for this issue* is using multiple users for different kubeconfig
files. See how to add more users in <<_sec.admin.security.users.add>>.
You can also check information about the user and the respective OIDC tokens in the kubeconfig file under the `users` section:

-----
users:
- name: myuser
user:
auth-provider:
config:
client-id: oidc
client-secret: <SECRET>
id-token: <ID_TOKEN>
idp-issuer-url: https://<IP>:<PORT>
refresh-token: <REFRESH_TOKEN>
name: oidc
-----


==== Access {kube} Resources

The user can now access resources in the authorized `<NAMESPACE>`.
Expand Down
5 changes: 4 additions & 1 deletion adoc/admin-security-user-group-management.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,5 @@
[[_sec.admin.security.users]]

= Managing Users and Groups

You can use standard LDAP administration tools for managing organizations, groups and users remotely.
Expand Down Expand Up @@ -107,6 +109,7 @@ DS_DM_PASSWORD= # Admin Password
ldapmodify -v -H <LDAP_PROTOCOL>://<LDAP_NODE_FQDN><LDAP_NODE_PROTOCOL> -D "<BIND_DN>" -f <LDIF_FILE> -w <DS_DM_PASSWORD>
----

[[_sec.admin.security.users.add]]
=== Adding a New User

. To add a new user, create an LDIF file (`new_user.ldif`) like this:
Expand Down Expand Up @@ -292,4 +295,4 @@ DS_DM_PASSWORD= # Old Password
NEW_DS_DM_PASSWORD= # New Password

ldappasswd -v -H <LDAP_PROTOCOL>://<LDAP_NODE_FQDN><LDAP_NODE_PROTOCOL> -x -D "<BIND_DN>" -w <DS_DM_PASSWORD> -a <DS_DM_PASSWORD> -s <NEW_DS_DM_PASSWORD>
----
----