[
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
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
>
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
[
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
> ---
>
>
[
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:
[
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
>
[
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
[
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
[
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
[
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
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:
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
[
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
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?
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
[
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
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.
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
[
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
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
[
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
> -
>
>
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
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
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 +
[
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"
>
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
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
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
[
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
> --
>
>
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
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
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
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:
33 matches
Mail list logo