Re: Some Console issues when creating Groups for 2.0.0-M2
On Thu, Mar 24, 2016 at 3:45 PM, Francesco Chicchiriccò wrote: Ok, so the "non-standard" step is > > cp core/src/main/resources/domains/MasterContent.xml > core/src/test/resources/domains > > this means that the "production" content for the Master domain is somewhat > broken: can you open a further issue for this? Thanks! > > Sure: https://issues.apache.org/jira/browse/SYNCOPE-814 Colm. > > Regards. > > -- > Francesco Chicchiriccò > > Tirasa - Open Source Excellence > http://www.tirasa.net/ > > Involved at The Apache Software Foundation: > member, Syncope PMC chair, Cocoon PMC, Olingo PMC, CXF committer > http://home.apache.org/~ilgrosso/ > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
Re: Some Console issues when creating Groups for 2.0.0-M2
On 24/03/2016 16:40, Colm O hEigeartaigh wrote: Hi Francesco, On Thu, Mar 24, 2016 at 3:16 PM, Francesco Chicchiriccò wrote: How could you get a group having "authentication.statuses" or other conf params as attributes? Which auxiliary classes have you selected? Selecting configuration parameters for AnyTypeClasses should not be allowed. Ok here are the steps to reproduce: a) Built the 2.0.0-M2 tag locally + create a new archetype project b) cd ; cp core/src/main/resources/domains/MasterContent.xml core/src/test/resources/domains c) mvn clean package + launch the console via mvn -Pembedded Now in the browser: Now just click on realms, Group + create a new group.Continue hitting "Next" without changing anything (in particular, without selecting a "Profile extension by auxiliary class" - I think this is where the bug is). Then you see the screenshot I attached. Ok, so the "non-standard" step is cp core/src/main/resources/domains/MasterContent.xml core/src/test/resources/domains this means that the "production" content for the Master domain is somewhat broken: can you open a further issue for this? Thanks! Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Involved at The Apache Software Foundation: member, Syncope PMC chair, Cocoon PMC, Olingo PMC, CXF committer http://home.apache.org/~ilgrosso/
Re: Some Console issues when creating Groups for 2.0.0-M2
Hi Francesco, On Thu, Mar 24, 2016 at 3:16 PM, Francesco Chicchiriccò wrote: > > How could you get a group having "authentication.statuses" or other conf > params as attributes? Which auxiliary classes have you selected? > Selecting configuration parameters for AnyTypeClasses should not be > allowed. > Ok here are the steps to reproduce: a) Built the 2.0.0-M2 tag locally + create a new archetype project b) cd ; cp core/src/main/resources/domains/MasterContent.xml core/src/test/resources/domains c) mvn clean package + launch the console via mvn -Pembedded Now in the browser: Now just click on realms, Group + create a new group.Continue hitting "Next" without changing anything (in particular, without selecting a "Profile extension by auxiliary class" - I think this is where the bug is). Then you see the screenshot I attached. Colm. > Regards. > > -- > Francesco Chicchiriccò > > Tirasa - Open Source Excellence > http://www.tirasa.net/ > > Involved at The Apache Software Foundation: > member, Syncope PMC chair, Cocoon PMC, Olingo PMC, CXF committer > http://home.apache.org/~ilgrosso/ > > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
Re: Some Console issues when creating Groups for 2.0.0-M2
On 24/03/2016 16:06, Colm O hEigeartaigh wrote: Thanks for your feedback Fabio. On Thu, Mar 24, 2016 at 1:44 PM, Fabio Martelli wrote: a) When browsing the Configuration Parameters, there appears to be no way to see whether a given parameter is "mandatory" or not. If you edit a parameter, you just see the Schema name + Values. Configuration parameters are optional (as is for 1.2.X). The issue is: mandatory field must be removed from configuration parameter creation page. https://issues.apache.org/jira/browse/SYNCOPE-813 b) When creating a new Group (Syncope embedded mode using the "main" MasterContent.xml) there is no "*" beside the "authentication.statuses" parameter (maybe because it is multi-valued?) However, if you fail to specify a value you get an error 'authentication.statuses is required'. Sorry but you shouldn't have authentication.statuses for group. Are you referring to configuration parameters? In this case see response above. No, I think maybe this is a separate bug, where Configuration Parameters are appearing when configuring a group. See the screenshot here: https://issues.apache.org/jira/secure/attachment/12795207/syncope-spinner.png You can see here that it is asking to specify items such as "password.cipher.algorithm" when creating a group? BTW this only happens when I don't select a value for "Profile extension by auxiliary classes". How could you get a group having "authentication.statuses" or other conf params as attributes? Which auxiliary classes have you selected? Selecting configuration parameters for AnyTypeClasses should not be allowed. Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Involved at The Apache Software Foundation: member, Syncope PMC chair, Cocoon PMC, Olingo PMC, CXF committer http://home.apache.org/~ilgrosso/
Re: Some Console issues when creating Groups for 2.0.0-M2
Thanks for your feedback Fabio. On Thu, Mar 24, 2016 at 1:44 PM, Fabio Martelli wrote: > > a) When browsing the Configuration Parameters, there appears to be no way >> to see whether a given parameter is "mandatory" or not. If you edit a >> parameter, you just see the Schema name + Values. >> > Configuration parameters are optional (as is for 1.2.X). > The issue is: mandatory field must be removed from configuration parameter > creation page. > https://issues.apache.org/jira/browse/SYNCOPE-813 > >> b) When creating a new Group (Syncope embedded mode using the "main" >> MasterContent.xml) there is no "*" beside the "authentication.statuses" >> parameter (maybe because it is multi-valued?) However, if you fail to >> specify a value you get an error 'authentication.statuses is required'. >> > Sorry but you shouldn't have authentication.statuses for group. > Are you referring to configuration parameters? In this case see response > above. > No, I think maybe this is a separate bug, where Configuration Parameters are appearing when configuring a group. See the screenshot here: https://issues.apache.org/jira/secure/attachment/12795207/syncope-spinner.png You can see here that it is asking to specify items such as "password.cipher.algorithm" when creating a group? BTW this only happens when I don't select a value for "Profile extension by auxiliary classes". Colm. > Colm. > > -- Fabio Martelli https://it.linkedin.com/pub/fabio-martelli/1/974/a44 http://blog.tirasa.net/author/fabio/index.html Tirasa - Open Source Excellence http://www.tirasa.net/ Apache Syncope PMC http://people.apache.org/~fmartelli/ -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
Re: Some Console issues when creating Groups for 2.0.0-M2
Hi Colm, please see my comment in-line. Regards, F. Il 24/03/2016 13:23, Colm O hEigeartaigh ha scritto: Hi all, More potential issues in 2.0.0-M2. Please give me some feedback + I will create JIRAs if necessary. a) When browsing the Configuration Parameters, there appears to be no way to see whether a given parameter is "mandatory" or not. If you edit a parameter, you just see the Schema name + Values. Configuration parameters are optional (as is for 1.2.X). The issue is: mandatory field must be removed from configuration parameter creation page. b) When creating a new Group (Syncope embedded mode using the "main" MasterContent.xml) there is no "*" beside the "authentication.statuses" parameter (maybe because it is multi-valued?) However, if you fail to specify a value you get an error 'authentication.statuses is required'. Sorry but you shouldn't have authentication.statuses for group. Are you referring to configuration parameters? In this case see response above. c) When creating a new Group, why not have the ability to select the given value from a drop down list according to the values configured for the parameter? So for example, if the value of "Password Cipher Algorithm" is "SHA1", then you should be able to select this from a drop down list. Maybe if there is only a single value, then it could already be filled in for you. Probably you are still referring to parameters. In any case you have this behaviour if you create an enum schema. d) If you make an error when configuring the Group, so for example as above if you don't fill in a value for "authentication.statuses", the values you have entered are wiped clean and you have to re-enter everything again. This is a bug. Can you open a new issue for this? e) If you enter a value for a multi-valued field (like "authentication.statuses") and then click "+" to add another, but then change your mind and click "-", the extra field stays put, there is no way to get rid of it. Sorry I cannot reproduce. Am I missing something? Colm. -- Fabio Martelli https://it.linkedin.com/pub/fabio-martelli/1/974/a44 http://blog.tirasa.net/author/fabio/index.html Tirasa - Open Source Excellence http://www.tirasa.net/ Apache Syncope PMC http://people.apache.org/~fmartelli/
Some Console issues when creating Groups for 2.0.0-M2
Hi all, More potential issues in 2.0.0-M2. Please give me some feedback + I will create JIRAs if necessary. a) When browsing the Configuration Parameters, there appears to be no way to see whether a given parameter is "mandatory" or not. If you edit a parameter, you just see the Schema name + Values. b) When creating a new Group (Syncope embedded mode using the "main" MasterContent.xml) there is no "*" beside the "authentication.statuses" parameter (maybe because it is multi-valued?) However, if you fail to specify a value you get an error 'authentication.statuses is required'. c) When creating a new Group, why not have the ability to select the given value from a drop down list according to the values configured for the parameter? So for example, if the value of "Password Cipher Algorithm" is "SHA1", then you should be able to select this from a drop down list. Maybe if there is only a single value, then it could already be filled in for you. d) If you make an error when configuring the Group, so for example as above if you don't fill in a value for "authentication.statuses", the values you have entered are wiped clean and you have to re-enter everything again. e) If you enter a value for a multi-valued field (like "authentication.statuses") and then click "+" to add another, but then change your mind and click "-", the extra field stays put, there is no way to get rid of it. Colm. -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
