[jira] [Commented] (SYNCOPE-811) Error message "'spinner' is required"

[Colm O hEigeartaigh (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210603#comment-15210603
 ] 

Colm O hEigeartaigh commented on SYNCOPE-811:
-

As SYNCOPE-814 appears to be the root cause here, this issue might be resolved 
by fixing SYNCOPE-814, as normally one shouldn't see the configuration 
parameters when editing a group...

> Error message "'spinner' is required"
> -
>
> Key: SYNCOPE-811
> URL: https://issues.apache.org/jira/browse/SYNCOPE-811
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.0-M2
>Reporter: Colm O hEigeartaigh
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: syncope-spinner.png
>
>
> If you don't specify a value when configuring a Group for a required (int) 
> parameter, you get a generic error message "'spinner' is required". Instead, 
> the error message should display the name of the parameter.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Some Console issues when creating Groups for 2.0.0-M2

[Colm O hEigeartaigh]

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

[jira] [Created] (SYNCOPE-814) MasterContent.xml configuration is broken for "main"

[Colm O hEigeartaigh (JIRA)]

Colm O hEigeartaigh created SYNCOPE-814:
---

 Summary: MasterContent.xml configuration is broken for "main"
 Key: SYNCOPE-814
 URL: https://issues.apache.org/jira/browse/SYNCOPE-814
 Project: Syncope
  Issue Type: Bug
Affects Versions: 2.0.0-M2
Reporter: Colm O hEigeartaigh
Priority: Minor
 Fix For: 2.0.0


The "production" content for the Master domain is somewhat broken. When 
creating a new group, you see the configuration parameters if you don't select 
an auxiliary class.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (SYNCOPE-765) Provide approval management

[fabio martelli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

fabio martelli resolved SYNCOPE-765.

Resolution: Fixed

> Provide approval management
> ---
>
> Key: SYNCOPE-765
> URL: https://issues.apache.org/jira/browse/SYNCOPE-765
> Project: Syncope
>  Issue Type: Sub-task
>  Components: console
>Reporter: Francesco Chicchiriccò
>Assignee: fabio martelli
> Fix For: 2.0.0
>
>
> Bring back the approval management features from 1.2, possibly leveraging the 
> Admin LTE widget for unread communications on the top right corner, right 
> next username.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (SYNCOPE-812) Remove flickering

[fabio martelli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

fabio martelli resolved SYNCOPE-812.

Resolution: Fixed

> Remove flickering
> -
>
> Key: SYNCOPE-812
> URL: https://issues.apache.org/jira/browse/SYNCOPE-812
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.0-M1
>Reporter: fabio martelli
>Assignee: fabio martelli
> Fix For: 2.0.0
>
>
> Browse console and remove flickering if useless.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (SYNCOPE-813) Remove "mandatory" field from configuration parameter creation

[fabio martelli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

fabio martelli resolved SYNCOPE-813.

Resolution: Fixed

> Remove "mandatory" field from configuration parameter creation
> --
>
> Key: SYNCOPE-813
> URL: https://issues.apache.org/jira/browse/SYNCOPE-813
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.0-M2
>Reporter: Colm O hEigeartaigh
>Assignee: fabio martelli
>Priority: Minor
> Fix For: 2.0.0
>
>
> This task is to remove the "mandatory" field from the Configuration Parameter 
> creation page, as Configuration Parameters are optional. Also, remove from 
> sample configuration (e.g. in MasterContent.xml):
> mandatoryCondition="true" multivalue="1" uniqueConstraint="0" 
> readonly="0"/>



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SYNCOPE-812) Remove flickering

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210516#comment-15210516
 ] 

ASF subversion and git services commented on SYNCOPE-812:
-

Commit 6dd1757b3ef536f56016693a320c5898084a9e1e in syncope's branch 
refs/heads/master from [~fmartelli]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=6dd1757 ]

[SYNCOPE-812] remove main flickerings


> Remove flickering
> -
>
> Key: SYNCOPE-812
> URL: https://issues.apache.org/jira/browse/SYNCOPE-812
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.0-M1
>Reporter: fabio martelli
>Assignee: fabio martelli
> Fix For: 2.0.0
>
>
> Browse console and remove flickering if useless.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SYNCOPE-765) Provide approval management

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210519#comment-15210519
 ] 

ASF subversion and git services commented on SYNCOPE-765:
-

Commit 9014cf2873b522d9fdd7dfe7afa5bdc8be3c9677 in syncope's branch 
refs/heads/master from [~fmartelli]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=9014cf2 ]

[SYNCOPE-765] providing TODO features


> Provide approval management
> ---
>
> Key: SYNCOPE-765
> URL: https://issues.apache.org/jira/browse/SYNCOPE-765
> Project: Syncope
>  Issue Type: Sub-task
>  Components: console
>Reporter: Francesco Chicchiriccò
>Assignee: fabio martelli
> Fix For: 2.0.0
>
>
> Bring back the approval management features from 1.2, possibly leveraging the 
> Admin LTE widget for unread communications on the top right corner, right 
> next username.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SYNCOPE-813) Remove "mandatory" field from configuration parameter creation

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210518#comment-15210518
 ] 

ASF subversion and git services commented on SYNCOPE-813:
-

Commit 762178b15fb3555c58813ede0caa87d9740f9064 in syncope's branch 
refs/heads/master from [~fmartelli]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=762178b ]

[SYNCOPE-813] mandatory condition for configuration parameters not available 
anymore from administration console


> Remove "mandatory" field from configuration parameter creation
> --
>
> Key: SYNCOPE-813
> URL: https://issues.apache.org/jira/browse/SYNCOPE-813
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.0-M2
>Reporter: Colm O hEigeartaigh
>Assignee: fabio martelli
>Priority: Minor
> Fix For: 2.0.0
>
>
> This task is to remove the "mandatory" field from the Configuration Parameter 
> creation page, as Configuration Parameters are optional. Also, remove from 
> sample configuration (e.g. in MasterContent.xml):
> mandatoryCondition="true" multivalue="1" uniqueConstraint="0" 
> readonly="0"/>



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SYNCOPE-812) Remove flickering

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210517#comment-15210517
 ] 

ASF subversion and git services commented on SYNCOPE-812:
-

Commit d9ec96b7c5d0c0dee206781e2c76f60eedcfe620 in syncope's branch 
refs/heads/master from [~fmartelli]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=d9ec96b ]

[SYNCOPE-812] fix for all useless flickering


> Remove flickering
> -
>
> Key: SYNCOPE-812
> URL: https://issues.apache.org/jira/browse/SYNCOPE-812
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.0-M1
>Reporter: fabio martelli
>Assignee: fabio martelli
> Fix For: 2.0.0
>
>
> Browse console and remove flickering if useless.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[ANN] Apache Syncope 2.0.0-M2 released

[Francesco Chicchiriccò]

The Apache Syncope team is pleased to announce the release of Syncope 
2.0.0-M2.


Apache Syncope is an Open Source system for managing digital identities
in enterprise environments, implemented in Java EE technology .

The release will be available within 24h from:
http://syncope.apache.org/downloads.html

The full change log is available here:
https://s.apache.org/syncope200M2

We welcome your help and feedback. For more information on how to report
problems, and to get involved, visit the project website at

http://syncope.apache.org/

The Apache Syncope Team

[RESULT] [VOTE] Apache Syncope 2.0.0-M2

[Francesco Chicchiriccò]

Hi all,
after 72 hours, the vote for Syncope 2.0.0-M2 [1] *passes* with 5 PMC + 
2 non-PMC votes.


+1 (PMC / binding)
* Francesco Chicchiriccò
* Marco Di Sabatino
* Fabio Martelli
* Massimiliano Perrone
* Colm O hEigeartaigh

+1 (non binding)
* Andrea Patricelli
* Giacomo Lamonaco

0


-1


Thanks to everyone participating.

I will now copy this release to Syncope's dist directory and promote the 
artifacts to the central Maven repository.


Best regards.

[1] http://markmail.org/message/ty4amo7bbxx3wcat

--
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/

[jira] [Commented] (SYNCOPE-701) New end-user UI

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210472#comment-15210472
 ] 

ASF subversion and git services commented on SYNCOPE-701:
-

Commit 0b4c4c8912daff5c22502467b2d743d525e3fa5a in syncope's branch 
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=0b4c4c8 ]

[SYNCOPE-701] Various improvements


> New end-user UI
> ---
>
> Key: SYNCOPE-701
> URL: https://issues.apache.org/jira/browse/SYNCOPE-701
> Project: Syncope
>  Issue Type: New Feature
>Reporter: Francesco Chicchiriccò
>Assignee: Andrea Patricelli
> Fix For: 2.0.0
>
>
> Before SYNCOPE-156, the admin console used to offer self-service features 
> like as self-registration, profile maintenance and password reset.
> The idea is to built a separate web application providing such features; some 
> requirements:
>  # extremely customizable on deployment basis: not only look & feel, but also 
> application logic (this sets one of glamour JS frameworks -as AngularJS - as 
> candidate)
>  # keep admin UI attitude of being gateway for accessing REST services 
> exposed by core: this might require to build a sort of 'proxy' application to 
> be contacted by client-side JS code



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Some Console issues when creating Groups for 2.0.0-M2

[Francesco Chicchiriccò]

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

[Colm O hEigeartaigh]

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

[jira] [Assigned] (SYNCOPE-813) Remove "mandatory" field from configuration parameter creation

[fabio martelli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

fabio martelli reassigned SYNCOPE-813:
--

Assignee: fabio martelli

> Remove "mandatory" field from configuration parameter creation
> --
>
> Key: SYNCOPE-813
> URL: https://issues.apache.org/jira/browse/SYNCOPE-813
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.0-M2
>Reporter: Colm O hEigeartaigh
>Assignee: fabio martelli
>Priority: Minor
> Fix For: 2.0.0
>
>
> This task is to remove the "mandatory" field from the Configuration Parameter 
> creation page, as Configuration Parameters are optional. Also, remove from 
> sample configuration (e.g. in MasterContent.xml):
> mandatoryCondition="true" multivalue="1" uniqueConstraint="0" 
> readonly="0"/>



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Some Console issues when creating Groups for 2.0.0-M2

[Francesco Chicchiriccò]

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

[Colm O hEigeartaigh]

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

[jira] [Updated] (SYNCOPE-813) Remove "mandatory" field from configuration parameter creation

[Colm O hEigeartaigh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Colm O hEigeartaigh updated SYNCOPE-813:

Description: 
This task is to remove the "mandatory" field from the Configuration Parameter 
creation page, as Configuration Parameters are optional. Also, remove from 
sample configuration (e.g. in MasterContent.xml):




  was:

This task is to remove the "mandatory" field from the Configuration Parameter 
creation page, as Configuration Parameters are optional.


> Remove "mandatory" field from configuration parameter creation
> --
>
> Key: SYNCOPE-813
> URL: https://issues.apache.org/jira/browse/SYNCOPE-813
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.0-M2
>Reporter: Colm O hEigeartaigh
>Priority: Minor
> Fix For: 2.0.0
>
>
> This task is to remove the "mandatory" field from the Configuration Parameter 
> creation page, as Configuration Parameters are optional. Also, remove from 
> sample configuration (e.g. in MasterContent.xml):
> mandatoryCondition="true" multivalue="1" uniqueConstraint="0" 
> readonly="0"/>



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SYNCOPE-813) Remove "mandatory" field from configuration parameter creation

[Colm O hEigeartaigh (JIRA)]

Colm O hEigeartaigh created SYNCOPE-813:
---

 Summary: Remove "mandatory" field from configuration parameter 
creation
 Key: SYNCOPE-813
 URL: https://issues.apache.org/jira/browse/SYNCOPE-813
 Project: Syncope
  Issue Type: Bug
  Components: console
Affects Versions: 2.0.0-M2
Reporter: Colm O hEigeartaigh
Priority: Minor
 Fix For: 2.0.0



This task is to remove the "mandatory" field from the Configuration Parameter 
creation page, as Configuration Parameters are optional.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (SYNCOPE-812) Remove flickering

[fabio martelli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

fabio martelli reassigned SYNCOPE-812:
--

Assignee: fabio martelli

> Remove flickering
> -
>
> Key: SYNCOPE-812
> URL: https://issues.apache.org/jira/browse/SYNCOPE-812
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.0-M1
>Reporter: fabio martelli
>Assignee: fabio martelli
> Fix For: 2.0.0
>
>
> Browse console and remove flickering if useless.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SYNCOPE-812) Remove flickering

[fabio martelli (JIRA)]

fabio martelli created SYNCOPE-812:
--

 Summary: Remove flickering
 Key: SYNCOPE-812
 URL: https://issues.apache.org/jira/browse/SYNCOPE-812
 Project: Syncope
  Issue Type: Bug
  Components: console
Affects Versions: 2.0.0-M1
Reporter: fabio martelli
 Fix For: 2.0.0


Browse console and remove flickering if useless.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Some Console issues when creating Groups for 2.0.0-M2

[Fabio Martelli]

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

[Colm O hEigeartaigh]

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

[jira] [Updated] (SYNCOPE-811) Error message "'spinner' is required"

[Colm O hEigeartaigh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Colm O hEigeartaigh updated SYNCOPE-811:

Attachment: syncope-spinner.png

> Error message "'spinner' is required"
> -
>
> Key: SYNCOPE-811
> URL: https://issues.apache.org/jira/browse/SYNCOPE-811
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.0-M2
>Reporter: Colm O hEigeartaigh
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: syncope-spinner.png
>
>
> If you don't specify a value when configuring a Group for a required (int) 
> parameter, you get a generic error message "'spinner' is required". Instead, 
> the error message should display the name of the parameter.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SYNCOPE-811) Error message "'spinner' is required"

[Colm O hEigeartaigh (JIRA)]

Colm O hEigeartaigh created SYNCOPE-811:
---

 Summary: Error message "'spinner' is required"
 Key: SYNCOPE-811
 URL: https://issues.apache.org/jira/browse/SYNCOPE-811
 Project: Syncope
  Issue Type: Bug
  Components: console
Affects Versions: 2.0.0-M2
Reporter: Colm O hEigeartaigh
Priority: Minor
 Fix For: 2.0.0
 Attachments: syncope-spinner.png


If you don't specify a value when configuring a Group for a required (int) 
parameter, you get a generic error message "'spinner' is required". Instead, 
the error message should display the name of the parameter.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Some comments on Connectors

[Francesco Chicchiriccò]

On 23/03/2016 17:55, Colm O hEigeartaigh wrote:

On Wed, Mar 23, 2016 at 4:35 PM, Francesco Chicchiriccò  
wrote:


a) I filed a bug (SYNCOPE-805) for when the user doesn't specify a

destination realm for a pull task. However, I wonder if it would it be
possible for the user to select the destination realm from a drop-down
list?

Sounds good: can you suggest this as alternative fix for SYNCOPE-805?

Done.


Thanks.


b) When running Syncope via a Maven archetype + mvn -Pembedded (using the core 
main, not test, configuration) I don't see anything relating to
"Extensions" in the UI. I see it when I download the standalone
distribution though. Perhaps the default configuration for the archetype
needs to be updated to reference Camel etc?

The idea is to not enable extensions (nor Camel nor Swagger UI, which are
the extensions currently available) by default; maybe an idea is to add a
further "all" profile - similarly to what we do with fit/core-reference so
that one can run

* mvn -Pembedded to get the environment without extensions
* mvn -Pembedded,all to get the environment with extensions

Yep that'd be great.


I have opened SYNCOPE-810.


c) I noticed here (https://dist.apache.org/repos/dist/dev/syncope/2.0.0-M2/)
that half of the artifacts start with "apache-syncope" and the other half
with "syncope". Any reason why they are not all starting with
"apache-syncope" for consistency?

Essentially, .deb packages have the "apache-syncope" prefix rather than
"syncope" - as all other artifacts, which take the name off of Maven
modules, do instead.

We might want to change the .deb packages prefix to "syncope" (and
generated directories as /etc/apache-syncope, /var/log/apache-syncope etc)
for consistency; anyway, this is following the practice we have since 1.2.0.

Ok thanks for the explanation. TBH I wouldn't bother changing things, it's
just a trivial issue really.


Fine: if others want, I don't see any troubles in renaming .deb packages.

Regards.


On Wed, Mar 23, 2016 at 3:56 PM, Colm O hEigeartaigh 

wrote:

Answers inline:

On Tue, Mar 22, 2016 at 3:49 PM, Francesco Chicchiriccò <
ilgro...@apache.org> wrote:

On 22/03/2016 15:09, Colm O hEigeartaigh wrote:

a) In the "Capabilities" tab, the header is "capabilitiesPalette" which

seems a bit unnecessary IMO. An "all" checkbox would possibly be useful
here which would select all of the other checkboxes.

Agree: would you mind opening an improvement for this?

https://issues.apache.org/jira/browse/SYNCOPE-802


b) In the "Configuration" tab, it's not clear to me what the On/Off

buttons
mean?


As for 1.2, such buttons sets the possibility to override the related
properties in the resources using the given connector.
I agree it is not clear now: again, could you please take care of filing
another improvement for this?


https://issues.apache.org/jira/browse/SYNCOPE-803

c) In previous Syncope versions, one could hover over the textfields IIRC

and get an explanation as to what the configuration item meant. However
this is not working, unless I am missing something.

Once more, I agree with you; third required improvement in a row.

https://issues.apache.org/jira/browse/SYNCOPE-804

d) Not related to Connectors, but I noticed that all of the table

listings


in the UI have both the header and footer containing the column names.
IMO
it would be sufficient just to have the header there.

This was set according to the Admin LTE template that we have chosen

for
the new admin console: see [1]; however, as you can imagine, we can
easily
revert to the single-header version; it's more a matter of taste.


Sure, it's not an important issue anyway.

Colm.

WDYT?

Regards.

[1] https://almsaeedstudio.com/themes/AdminLTE/pages/tables/data.html


--
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/

[jira] [Created] (SYNCOPE-810) Allow generated projects to include extensions in embedded mode

[JIRA]

Francesco Chicchiriccò created SYNCOPE-810:
--

 Summary: Allow generated projects to include extensions in 
embedded mode
 Key: SYNCOPE-810
 URL: https://issues.apache.org/jira/browse/SYNCOPE-810
 Project: Syncope
  Issue Type: Improvement
  Components: archetype
Reporter: Francesco Chicchiriccò
 Fix For: 2.0.0


Define an additional profile for {{core}} module (in the generated project) 
which works similarly to the profile with same name of {{fit/core-reference}} 
in project sources.

Update documentation accordingly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SYNCOPE-770) IDE plugin

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-770:
---
Labels:   (was: eclipse gsoc2016 netbeans)

> IDE plugin
> --
>
> Key: SYNCOPE-770
> URL: https://issues.apache.org/jira/browse/SYNCOPE-770
> Project: Syncope
>  Issue Type: New Feature
>Reporter: Francesco Chicchiriccò
>
> Develop plugin(s) for one or more popular open source IDEs (as Netbeans or 
> Eclipse) with purpose of easing the extension of runtime configuration of 
> Apache Syncope deployments.
> SYNCOPE-760 and SYNCOPE-761 introduced the possibility to dynamically reload 
> mail templates (used by notifications) and report stylesheets; such objects 
> are now exposed as REST entities.
> The idea is to enable IDEs with some kind of resource explorer providing 
> access to such dynamic items, allowing to create, edit and remove them from 
> within IDE, by connecting to a running Apache Syncope deployment.
> This item is being discussed at 
> https://cwiki.apache.org/confluence/display/SYNCOPE/GSOC+2016



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SYNCOPE-808) Netbeans plugin

[JIRA]

Francesco Chicchiriccò created SYNCOPE-808:
--

 Summary: Netbeans plugin
 Key: SYNCOPE-808
 URL: https://issues.apache.org/jira/browse/SYNCOPE-808
 Project: Syncope
  Issue Type: Sub-task
 Environment: Netbeans IDE
Reporter: Francesco Chicchiriccò


Develop a plug-in, according to what reported in SYNCOPE-770, working with 
latest Netbeans version.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Adding russian language to UI

[Dmitriy Berezkin]

Hi!
Thank you for worrying.
I cloned git, found all language *.properties files and almost finished
with "SyncopeConsoleApplication_ru.properties".
I didn't configured yet my dev environment to test my modifications, but
building project with mvn works fine.



2016-03-24 11:01 GMT+03:00 Francesco Chicchiriccò :

> Hi,
> any progress so far? Have you attempted the procedure described at [1]?
>
> Regards.
>
> On 22/03/2016 10:44, Francesco Chicchiriccò wrote:
>
>> On 22-mar-16, at 10:32, Francesco Chicchiriccò ilgro...@apache.org ha
>> scritto:
>>
>> On 22-mar-16, at 10:20, Dmitriy Berezkin berezkin.dmit...@gmail.com
>>> wrote:
>>>
>>> Hi all!

 I would like to translate syncope 2.0.0 UI to russian language. I'm
 looking
 for preinstalled environment to get started with syncope 2.0.0-M2.
 It will be great if russian language support for syncope UI will be OOTB
 for 2.0.0 release.

>>> Hi Dmitriy,
>>> this sounds just great; right now I am updating [1] which gives some
>>> indications
>>> and a draft procedure for adding new translations to the admin console.
>>>
>>> Once done I'll update there, stay tuned.
>>>
>> The page [1] is now updated: please take a look and let us know.
>> Regards.
>>
>> [1]
>>> https://cwiki.apache.org/confluence/display/SYNCOPE/Adding+new+language+to+admin+console+UI
>>>
>>
> --
> 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/
>
>

[jira] [Created] (SYNCOPE-807) When editing realms, select account and password policies from combo box

[JIRA]

Francesco Chicchiriccò created SYNCOPE-807:
--

 Summary: When editing realms, select account and password policies 
from combo box
 Key: SYNCOPE-807
 URL: https://issues.apache.org/jira/browse/SYNCOPE-807
 Project: Syncope
  Issue Type: Improvement
  Components: console
Reporter: Francesco Chicchiriccò
 Fix For: 2.0.0


As done when editing an external resource (under "Security"), allow selecting 
account and password policies from combo box, when editing realms.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Adding russian language to UI

[Francesco Chicchiriccò]

Hi,
any progress so far? Have you attempted the procedure described at [1]?

Regards.

On 22/03/2016 10:44, Francesco Chicchiriccò wrote:

On 22-mar-16, at 10:32, Francesco Chicchiriccò ilgro...@apache.org ha scritto:


On 22-mar-16, at 10:20, Dmitriy Berezkin berezkin.dmit...@gmail.com wrote:


Hi all!

I would like to translate syncope 2.0.0 UI to russian language. I'm looking
for preinstalled environment to get started with syncope 2.0.0-M2.
It will be great if russian language support for syncope UI will be OOTB
for 2.0.0 release.

Hi Dmitriy,
this sounds just great; right now I am updating [1] which gives some indications
and a draft procedure for adding new translations to the admin console.

Once done I'll update there, stay tuned.

The page [1] is now updated: please take a look and let us know.
Regards.


[1] 
https://cwiki.apache.org/confluence/display/SYNCOPE/Adding+new+language+to+admin+console+UI


--
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/