Disabling Password Policies
by Bill Burke
I'm hiding/disabling Password Policies as they don't work:
* After adding a policy you refresh/revisit the page, the policy value
doesn't show up (although the value is saved in storage). This is an
angular issue.
* password policy is not checked for "update password" when logging in
(only for registration and Acct Service it seems).
Since we're very close to release, we can fix this after please.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
11 years, 11 months
Proposed changes to menu
by Stian Thorgersen
When writing documentation to using the admin console I realised the menus are confusing.
Most applications/websites have their main-menu at the top, with a sub-menu on the left (or right).
Also I don't think there's any benefit to the breadcrumbs as we never navigate deep enough for it to be useful.
I propose that we move the items from the menu to the left into the same menu as the realm selector. Then we move the sub-menu items into the left menu. And also remove the breadcrumb. See attached screenshot for how this would look like.
I think this is a significant improvement, and it would be worth to get this into the alpha1 IMO. I can have this tested and committed today if there's consent for it!
11 years, 11 months
Social updates and documentation
by Stian Thorgersen
I've done some updates to social login:
* Moved instructions for configuring providers from admin console to documentation
* Updated Google provider
* Updated/fixed instructions for all providers
The reason for all these changes was the other day I tried to enable social login and neither of the providers we have worked. It turns out that Google has changed their console and apis. Facebook had changed its console. Finally, Twitter hadn't changed console or apis, but now requires all traffic to be over https (making it more difficult to test during development).
The lesson learned IMO, is:
1) Use Keycloak to enable social login - otherwise you have to muck about this yourself
2) We need to automate testing of the social providers - doing this manually is a real PITA
11 years, 11 months
minor console changes
by Bill Burke
* When creating a realm, Require SSL is set to true if the admin console
was loaded with HTTPS, otherwise it is set to false.
* Default Roles page will show the "account" application by default.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
11 years, 11 months
minimum doc requirements?
by Bill Burke
What do we minimally need for documentation for Alpha 1?
* Install/Config Server
* Install/Config Adapters
I'm thinking that screencast tutorials would be much better than
documentation. IMO, its hard to document UIs. Its better just seeing
them in action, so for Alpha 1 I'll just do these screencast tutorials:
Tutorial #1:
* Create a realm through admin console for customer-portal demo
* Create roles, user, role mappings, scope mappings, applications etc.
* Obtain a keycloak.json file for the adapter configs.
* enable adapters for customer, product, and database portal.
Tutorial #2:
* Create an oauth-client
* configure third-party example and walk through it
* demo it.
Tutorial #3:
* Create a Google OAuth account
* Enable social login for demo
* Set up default roles
* Enable registration
Tutorial #4:
* Turning on TOTP.
* Managing users
Tutorial #5:
* Setting up SSL
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
11 years, 11 months
more things we need
by Bill Burke
One thing I notice from doing the tutorial:
* User account management should be turned on by default
* Default roles should be visible even without registration and
privileges should be automatic for the Account Server for all users.
* We don't need a User Account Management switch. Admins can just
choose to not set a default role for user account management.
I just think it will be rare to not have Acct Service turned off, so
might as well set it up by default.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
11 years, 11 months
