[#CONF-8907] Allow programmatic access to atlassian-user.xml

Confluence

Allow programmatic access to atlassian-user.xml

Created: 16/Jul/07 12:20 AM Updated: 06/Aug/07 02:39 PM

Component/s:

Administration, External User Management, Remote API (SOAP & XML-RPC), Usability, Users & Groups

Affects Version/s:

2.5.4

Fix Version/s:

None

Time Tracking:

Not Specified

File Attachments:

atlassian-user.zip (4 kB)

Issue Links:

Reference

This issue relates to:

~~CONF-7599~~ Automatically migrate Confluence installations to using Hibernate storage for atlassian-user users

This issue is related to:

CONF-7828 Ability to migrate users/group to LDAP repository

Participants:	Andy Brook, Andy Brook and Ivan Benko [Atlassian]
Since last comment:	1 year, 9 weeks ago
Labels:

Description

« Hide

Presently there is no programmatic way to obtain an LDAP connection details inside a plugin.

We would need to write a parser with a flexible file format to accommodate for changes being made in the future.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Andy Brook added a comment - 16/Jul/07 03:45 AM

Given that atlassian-user.xml is the 'way forward', it would be useful if the parser could handle generic 'properties' just like osuser.xml used to do. For example, to pass the referral environment flag through to confluence - osuser.xml allowed this, atlassian-user.xml does not...

[ Permlink | « Hide ]

Andy Brook added a comment - 06/Aug/07 02:39 PM

Heres a commons Digester based parser I just wrote for the atlassian-user.xml file, if it were bundled somewhere within confluence, programmatic access to LDAP configuration would be exposed for plugin usage.

Take it, chop it, use, it , with my blessing. Need something more with it? comment.