How do you access or enable the old KeyCloak user account console? In this blog post about the new user account console, they say "The old account console is still available for those who need it", but I cannot find out where to enable that.
You need to :
Go to your Realm;
And in Account Theme explicitly chose "keycloak"
Click Save
In the Account dropdown menu you will see at least the follow:
base;
keycloak;
keycloak.v2.
By default the new version is selected keycloak.v2. keycloak refers to the "old" version.
Related
I created a client called my-app in myrealm realm, the Always Display in Console and Consent Required options of which are also enabled.
According to the help message of the Always Display in Console option which says:
Always list this client in the Account Console, even if the user does not have a active session.
And then, I logged in the user console via <mydomain>/auth/realms/myrealm/account, but there is no application named my-app in the application (only one named Account Console listed here).
Is there anything I missed for the configurations?
I tried filling out the Base URL field on the client, and the application was listed in the Application List in the Account Console.
KeyCloak Account Management Console
How do I disable the menus authenticator, sessions, applications, log and my resources options from the Account Management Console in KeyCloak as marked in the picture? I just want to have the Account and Password option to be available for the users.
Are you using the new or the old account console?
With the new account console you may simply want to adjust the content.json file
Check out this quickstart for details
With the old account console, I guess you will need to adjust the template.ftl in your own theme.
Note: Please be aware that this will only change the theme and users will still be able to use the APIs directly.
I am getting error to configure the OAuth in the che.property. but I am not able to find the location of the file and the syntax to add the configurations. I am using Ubuntu 18.04
For single-user Che, see https://www.eclipse.org/che/docs/che-7/version-control/#configuring-github-oauth_version-control.
For multi-user Che:
Go to the keycloak page (http://keycloak-che.192.168.99.170.nip.io/)
login as admin
click Identity Providers.
In the Add provider drop-down list, click GitHub. The Add identity provider window is displayed.
In the Add identity provider window:
The Redirect URI field, depending on your Eclipse Che installation,
type the Authorization callback URL.
Copy the client ID and the client secret from GitHub and paste them
in the Client ID and the Client Secret fields, respectively.
In the Homepage URL and the Authorization callback URL field,
depending on your Eclipse Che installation, type the two URLS.
In the Default Scopes field, type repo, user, write:publick_key.
Set Store Tokens and Stored Tokens Readable to ON.
Click Save.
The Success! The github provider has been created. message indicates success. And, the GitHub provider is added to the Identity Providers window.
Perform the following steps to set role mapping for non-administrative users.
Expand the Manage tab and then click Users.
Click the Role Mappings tab.
Click the Client Roles drop-down menu and click broker.
In the Available Roles list, click read-token.
Click Add selected.
In the Effective Roles list, click read-token.
The GitHub OAuth is now set for the user.
Numerous forum posts and documentations specify extracting login info for the Kubernetes install from ~/.kube/config.
The problem I found: mine doesn't have a proper user account, it specifies a name and a token.
How do I get the account name so I can use the kubernetes-cockpit UI? Surprisingly there appears to be nothing on that topic - what to do if the config doesn't contain an account.
It depends on how you use Cockpit.
According to cockpit official page:
Used in a standard cockpit session:
If a user is able to use kubectl successfully when at their shell terminal, then that same user will able to use Kubernetes dashboard when logged into Cockpit
I suppose this is your scenario, so if you didn't change default settings, the cockpit will look for .kube/config itself, i.e. you should be able to login without specifying your account.
I read the moodle user:update document. The Manager supposed to have the update user profile permission.
I have assigned a user with Manager systemwide role.
I checked on the Manager role on moodle/user:update, it is set to Allow.
I checked on the user permission, moodle/user:update is set to No
The user is inheriting the following roles.
Manager in System
Authenticated user in System
Can someone give me a clue? or is there any tools I can use to debug which rules override the status?
Thanks.
It is a bug. The fix will be released next week.
I am using version Moodle 2.8.3+ (Build: 20150205).
https://tracker.moodle.org/browse/MDL-50917