[
https://jira.duraspace.org/browse/DS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20942#action_20942
]
Stuart Lewis commented on DS-941:
---------------------------------
So it sounds like the best option in these case is to use the prefix for the
filename (e.g. ldap.cfg / sword.cfg / authentication.cfg) and then to remove
that from the keys when we transfer them - e.g. 'ldap.enable' become 'enable'.
However if we did that, then many will be in their own files (e.g. ldap)
however others such as x509 and shibboleth always use the 'authentication.'
prefix. What's the best thing here - re-work the code that reads those to drop
the 'authentication.'?
> Marker ticket for splitting up the dspace.cfg.
> -----------------------------------------------
>
> Key: DS-941
> URL: https://jira.duraspace.org/browse/DS-941
> Project: DSpace
> Issue Type: Improvement
> Reporter: Robin Taylor
> Fix For: 1.8.0
>
>
> Split dspace.cfg into separate files where appropriate.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
