Francesco, Thx for your patience, adding the *.*.layout multivalue string configuration did the trick!
I've found a little issue while adding an LDAP based role to a user that doesn't have the LDAP resource assigned: The LDAP provisioning fails on "missing required attribute __PASSWORD__" but the password is set using AES encryption and adding the resource explicitly for this user succeeds wihtout problem, so it's the "indirect" resource assignment that fails (as far as I understand the workings). You want me to report an issue for this? Best regards, Martin On Mon, Aug 24, 2015 at 9:59 AM, Francesco Chicchiriccò <[email protected]> wrote: > On 23/08/2015 13:01, Martin van Es wrote: >> >> On Sun, Aug 23, 2015 at 12:11 PM, Francesco Chicchiriccò >> <[email protected]> wrote: >>> >>> On 2015-08-23 10:45 Martin van Es wrote: >>>> >>>> Hi, >>>> >>>> I'm trying to configure a role membership attribute, but it doesn't >>>> show while adding a user to a role, >>> >>> >>> "It doesn't show up" because it is not supposed to do. >>> In order to being allowed to provide values for schema S in memberships >>> for >>> role R, you need to add an attribute template for S in R. You can do this >>> from admin console from the "Templates" tab in the edit window of role R. >> >> Ok, I got that "fixed" and can now set a membership attribute on the role. >> >>> Layouts are stored in configuration parameters: the first time that you >>> hit >>> save such configuration parameters are not yet in, and further save >>> should >>> work without any notice. (Actually, even this first error message >>> shouldn't >>> appear, I'll try tomorrow again with a fresh deb installation). >> >> No, repeatedly saving the layouts tab keeps showing up the error, and >> most important: the layouts aren't saved so the error does tell the >> truth (but that doesn't matter much to me anymore, because I achieved >> what I wanted to do ;) > > > Your problems are generated from the fact that you haven't neither performed > a clean 1.2.5 installation (because you've started from the content.xml > exported from previous version) nor followed any upgrade guide (I suppose). > > In order to "sanitize" your installation, you'll need to perform some steps, > namely [1] (if needed) and [2]. > > HTH > Regards. > > [1] > https://cwiki.apache.org/confluence/display/SYNCOPE/Upgrade+from+1.2.0-M1+to+1.2.0#Upgradefrom1.2.0-M1to1.2.0-Beforestarting > [2] > https://cwiki.apache.org/confluence/display/SYNCOPE/Upgrade+from+1.2.0+to+1.2.1#Upgradefrom1.2.0to1.2.1-Beforestarting > > > -- > Francesco Chicchiriccò > > Tirasa - Open Source Excellence > http://www.tirasa.net/ > > Involved at The Apache Software Foundation: > member, Syncope PMC chair, Cocoon PMC, Olingo PMC > http://people.apache.org/~ilgrosso/ > -- If 'but' was any useful, it would be a logic operator
