Bug 1146117 - Unable to set LDAP cache in security realms under "authorization=ldap/group-search=principal-to-group"
Summary: Unable to set LDAP cache in security realms under "authorization=ldap/group-s...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Security
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: DR3
: EAP 6.4.0
Assignee: Darran Lofthouse
QA Contact: Pavel Slavicek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-24 13:37 UTC by Josef Cacek
Modified: 2019-08-19 12:43 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:43:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker EAP6-191 0 Major Closed Management security realms should cache LDAP data 2016-01-22 13:16:00 UTC
Red Hat Issue Tracker WFCORE-125 0 Major Resolved Security realm cache definitions not possible for LDAP prinicipal to group group loading. 2016-01-22 13:16:00 UTC

Description Josef Cacek 2014-09-24 13:37:15 UTC
It's not possible to configure LDAP cache in security realms under "authorization=ldap/group-search=principal-to-group"

Possible reason:
The LdapCacheResourceDefinition is not registered under the org.jboss.as.domain.management.security.PrincipalToGroupResourceDefinition

When I try to add the cache configuration manually to standalone.xml, server doesn't start and reports:

15:23:44,619 ERROR [org.jboss.as.controller] (Controller Boot Thread) JBAS014629: No resource definition is registered for address [
    ("core-service" => "management"),
    ("security-realm" => "JBossTest"),
    ("authorization" => "ldap"),
    ("group-search" => "principal-to-group"),
    ("cache" => "by-search-time")
]
15:23:44,621 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.

Comment 2 Josef Cacek 2014-10-02 08:15:59 UTC
Verified in 6.4.0.DR3

CLI Steps:
/core-service=management/ldap-connection=ldapConnection:add(url="ldap://localhost:10389", search-credential="secret", search-dn="uid=admin,ou=system")
/core-service=management/security-realm=JBossTest:add
/core-service=management/security-realm=JBossTest/authentication=ldap:add(connection=ldapConnection, base-dn="dc=jboss,dc=org", recursive=true, username-attribute=uid)
batch
/core-service=management/security-realm=JBossTest/authorization=ldap:add(connection=ldapConnection)
/core-service=management/security-realm=JBossTest/authorization=ldap/group-search=principal-to-group:add(group-name=SIMPLE, group-name-attribute=cn, iterative=true, group-attribute=description)
run-batch
reload

Comment 3 JBoss JIRA Server 2015-04-28 15:05:19 UTC
John Doyle <jdoyle> updated the status of jira EAP6-191 to Closed


Note You need to log in before you can comment on or make changes to this bug.