Re: R: Password and account expiration features
On 12/03/2013 16:00, Denis Signoretto wrote: Hi Fabio, Thanks for your response. Do you think it could be useful open an issue on Jira for these features? (if yes a can do it). I take a quick look to SampleJob and AbstractTaskJob classes. I think it could be useful allow a scheduled task to have configuration parameters. I guess it's possible to define and read global configuration parameters within a SchedTask. What do you think about possibility to enhance SchedTask to define and store it's own configuration parameters? Hi Denis, you can define in any class extending AbstractTaskJob (as SampleJob for example) the field @Autowired private ConfDAO confDAO; and then access (read / write) any configuration parameter that you can also manage from the admin console, under the Configuration - Parameters. Is this what you are looking for? Regards. -Messaggio originale- Da: Fabio Martelli [mailto:fabio.marte...@gmail.com] Inviato: lunedì 11 marzo 2013 13:10 A: dev@syncope.apache.org Oggetto: Re: Password and account expiration features Il giorno 11/mar/2013, alle ore 12.50, Denis Signoretto ha scritto: Hi Syncopers, I'm currently using Syncope 1.0.6 and I've just checked on Syncope roadmap [1]. The following features doesn't seams available or already included in the roadmap (am I wrong) ? - Account Expiration (disable user on all resources that support enable/disable or change the password on resources that doesn't support it) Not yet available (explicitly, at least). This feature could be implemented by scheduling an ad-hoc SchedTask. - Password Expiration/Expired (force password change - on Syncope and resources**) Not yet available (explicitly, at least). This feature could be implemented by scheduling an ad-hoc SchedTask. - Grace Period: number of logins (or period) allowed after password expiration (on Syncope and resources**) Not yet available (explicitly, at least). This feature could be implemented by scheduling an ad-hoc SchedTask. - Account Lock (explicit or automatic lock for a certain amount of time after a number of wrong credentials - on Syncope and resources**) Already available. Configurable by an account policy. - Events/Notifications for account/password expiration, account/password expired, account locked Not yet available (explicitly, at least). This feature could be implemented by scheduling an ad-hoc SchedTask. Best regards, F. WDYT? Best regards. Denis. ** these features needs an enhanced connector that support it. [1] - https://cwiki.apache.org/confluence/display/SYNCOPE/Roadmap -- Francesco Chicchiriccò ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/
Re: R: Password and account expiration features
Il giorno 13/mar/2013, alle ore 09.09, Francesco Chicchiriccò ha scritto: On 12/03/2013 16:00, Denis Signoretto wrote: Hi Fabio, Thanks for your response. Do you think it could be useful open an issue on Jira for these features? (if yes a can do it). I take a quick look to SampleJob and AbstractTaskJob classes. I think it could be useful allow a scheduled task to have configuration parameters. I guess it's possible to define and read global configuration parameters within a SchedTask. What do you think about possibility to enhance SchedTask to define and store it's own configuration parameters? Hi Denis, you can define in any class extending AbstractTaskJob (as SampleJob for example) the field @Autowired private ConfDAO confDAO; and then access (read / write) any configuration parameter that you can also manage from the admin console, under the Configuration - Parameters. Is this what you are looking for? Hi Denis, I agree with Francesco: it should be better to use the global configuration parameters. From my PPOV the proposed SchedTask enhancement would require an big effort not so justified. Best regards, F. Regards. -Messaggio originale- Da: Fabio Martelli [mailto:fabio.marte...@gmail.com] Inviato: lunedì 11 marzo 2013 13:10 A: dev@syncope.apache.org Oggetto: Re: Password and account expiration features Il giorno 11/mar/2013, alle ore 12.50, Denis Signoretto ha scritto: Hi Syncopers, I'm currently using Syncope 1.0.6 and I've just checked on Syncope roadmap [1]. The following features doesn't seams available or already included in the roadmap (am I wrong) ? - Account Expiration (disable user on all resources that support enable/disable or change the password on resources that doesn't support it) Not yet available (explicitly, at least). This feature could be implemented by scheduling an ad-hoc SchedTask. - Password Expiration/Expired (force password change - on Syncope and resources**) Not yet available (explicitly, at least). This feature could be implemented by scheduling an ad-hoc SchedTask. - Grace Period: number of logins (or period) allowed after password expiration (on Syncope and resources**) Not yet available (explicitly, at least). This feature could be implemented by scheduling an ad-hoc SchedTask. - Account Lock (explicit or automatic lock for a certain amount of time after a number of wrong credentials - on Syncope and resources**) Already available. Configurable by an account policy. - Events/Notifications for account/password expiration, account/password expired, account locked Not yet available (explicitly, at least). This feature could be implemented by scheduling an ad-hoc SchedTask. Best regards, F. WDYT? Best regards. Denis. ** these features needs an enhanced connector that support it. [1] - https://cwiki.apache.org/confluence/display/SYNCOPE/Roadmap -- Francesco Chicchiriccò ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/
[jira] [Assigned] (SYNCOPE-336) Use a auto-complete textfield to chose for external attribute to be mapped during schema mapping creation
[ https://issues.apache.org/jira/browse/SYNCOPE-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli reassigned SYNCOPE-336: -- Assignee: fabio martelli Use a auto-complete textfield to chose for external attribute to be mapped during schema mapping creation - Key: SYNCOPE-336 URL: https://issues.apache.org/jira/browse/SYNCOPE-336 Project: Syncope Issue Type: Bug Components: console Reporter: fabio martelli Assignee: fabio martelli Fix For: 1.0.7, 1.1.0 Sometimes external resource can expect one or more special attribute, not explicitly included into the schema, to perform a certain operation. Think about ldapGroups for AD or LDAPv3 connectors. If a resource implement the schema method, the administration console won't give the possibility to map external attribute not included into the resource schema. This seems to be a great limitation that can be simply removed by changing the dropdown choice used to chose for an external attribute to be mapped with an auto-complete textfield. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-336) Use a auto-complete textfield to chose for external attribute to be mapped during schema mapping creation
[ https://issues.apache.org/jira/browse/SYNCOPE-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601031#comment-13601031 ] Hudson commented on SYNCOPE-336: Integrated in Syncope-1_0_X #160 (See [https://builds.apache.org/job/Syncope-1_0_X/160/]) SYNCOPE-336 fixed into the branch 1_0_X (Revision 1455848) Result = SUCCESS fmartelli : Files : * /syncope/branches/1_0_X/console/src/main/java/org/apache/syncope/console/pages/panels/ResourceMappingPanel.java * /syncope/branches/1_0_X/console/src/main/java/org/apache/syncope/console/wicket/markup/html/form/AjaxTextFieldPanel.java Use a auto-complete textfield to chose for external attribute to be mapped during schema mapping creation - Key: SYNCOPE-336 URL: https://issues.apache.org/jira/browse/SYNCOPE-336 Project: Syncope Issue Type: Bug Components: console Reporter: fabio martelli Assignee: fabio martelli Fix For: 1.0.7, 1.1.0 Sometimes external resource can expect one or more special attribute, not explicitly included into the schema, to perform a certain operation. Think about ldapGroups for AD or LDAPv3 connectors. If a resource implement the schema method, the administration console won't give the possibility to map external attribute not included into the resource schema. This seems to be a great limitation that can be simply removed by changing the dropdown choice used to chose for an external attribute to be mapped with an auto-complete textfield. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-210) Provide suggestions / help / examples for JEXL-based input fields
[ https://issues.apache.org/jira/browse/SYNCOPE-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601331#comment-13601331 ] Francesco Chicchiriccò commented on SYNCOPE-210: Please try to enlarge the modal window and check if the ? icon goes back to the same line. Provide suggestions / help / examples for JEXL-based input fields - Key: SYNCOPE-210 URL: https://issues.apache.org/jira/browse/SYNCOPE-210 Project: Syncope Issue Type: Improvement Components: console Reporter: Francesco Chicchiriccò Assignee: Massimiliano Perrone Fix For: 1.1.0 Attachments: one.png, two.png There are many input text fields accepting JEXL syntax: * derived schema definition (user / role / membership) * values for defining synchronization user template * schema mapping's mandatory condition * ... Users would benefit from some examples, help, suggestions, link to JEXL reference to be displayed in (or linked from) the web forms containing such input fields. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-210) Provide suggestions / help / examples for JEXL-based input fields
[ https://issues.apache.org/jira/browse/SYNCOPE-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601335#comment-13601335 ] Colm O hEigeartaigh commented on SYNCOPE-210: - Yup that works. So either we need to make the Mandatory Condition text field smaller (to the same size as name for example), or make the window wider. WDYT? Colm. Provide suggestions / help / examples for JEXL-based input fields - Key: SYNCOPE-210 URL: https://issues.apache.org/jira/browse/SYNCOPE-210 Project: Syncope Issue Type: Improvement Components: console Reporter: Francesco Chicchiriccò Assignee: Massimiliano Perrone Fix For: 1.1.0 Attachments: one.png, two.png There are many input text fields accepting JEXL syntax: * derived schema definition (user / role / membership) * values for defining synchronization user template * schema mapping's mandatory condition * ... Users would benefit from some examples, help, suggestions, link to JEXL reference to be displayed in (or linked from) the web forms containing such input fields. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-210) Provide suggestions / help / examples for JEXL-based input fields
[ https://issues.apache.org/jira/browse/SYNCOPE-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601341#comment-13601341 ] Francesco Chicchiriccò commented on SYNCOPE-210: +1 for making the window wider: having the Mandatory Condition text field too small might not be handful for putting JEXL expressions in there. Provide suggestions / help / examples for JEXL-based input fields - Key: SYNCOPE-210 URL: https://issues.apache.org/jira/browse/SYNCOPE-210 Project: Syncope Issue Type: Improvement Components: console Reporter: Francesco Chicchiriccò Assignee: Massimiliano Perrone Fix For: 1.1.0 Attachments: one.png, two.png There are many input text fields accepting JEXL syntax: * derived schema definition (user / role / membership) * values for defining synchronization user template * schema mapping's mandatory condition * ... Users would benefit from some examples, help, suggestions, link to JEXL reference to be displayed in (or linked from) the web forms containing such input fields. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Syncope-trunk - Build # 149 - Failure
The Apache Jenkins build system has built Syncope-trunk (build #149) Status: Failure Check console output at https://builds.apache.org/job/Syncope-trunk/149/ to view the results.
