Hey Bruno,
it seems Bill pushed already some LDAP changes last night and migrated
LDAP FederationProvider to UserStorage SPI. Do you have an opportunity
to retry with latest master? If it can be still reproduced, then you can
create JIRA for 2.4.1 fix version. We already have bunch of LDAP related
issues planned for that version, so this can be possibly another one to
address.
Marek
On 14/11/16 20:21, Bruno Oliveira wrote:
Good morning, I believe I found a bug while playing with LDAP
Federation
provider. But before file any Jira, I would like to confirm.
Steps to reproduce:
1. Just follow all the steps described here
https://github.com/keycloak/keycloak/tree/master/examples/ldap
2. Change the federation provider to read-only mode
3. Synchronize all users
4. Delete all the roles associated with LDAP (For example: ldap-user,
ldap-admin)
5. Now go to "Users" > "Edit"
6. Click on "Role Mappings"
You might get an exception like this:
https://gist.github.com/abstractj/19eb8e5f25fee3b469110246066ecd08
Is this a bug?
--
abstractj
PGP: 0x84DC9914
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev