Andrea Patricelli created SYNCOPE-1123:
--
Summary: Enduser UserRequestValidator NPE on custom form empty
sections
Key: SYNCOPE-1123
URL: https://issues.apache.org/jira/browse/SYNCOPE-1123
[
https://issues.apache.org/jira/browse/SYNCOPE-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061126#comment-16061126
]
ASF subversion and git services commented on SYNCOPE-1120:
--
Commit
[
https://issues.apache.org/jira/browse/SYNCOPE-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Patricelli reopened SYNCOPE-1116:
Align documentation accordin to new propagtion action
> Propagation action to manage
[
https://issues.apache.org/jira/browse/SYNCOPE-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Patricelli resolved SYNCOPE-1116.
Resolution: Fixed
> Propagation action to manage propagation on LDAP of realms
[
https://issues.apache.org/jira/browse/SYNCOPE-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061113#comment-16061113
]
ASF subversion and git services commented on SYNCOPE-1116:
--
Commit
[
https://issues.apache.org/jira/browse/SYNCOPE-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh resolved SYNCOPE-1120.
--
Resolution: Fixed
> Use the standard Bearer Authorization header for JWT
[
https://issues.apache.org/jira/browse/SYNCOPE-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061127#comment-16061127
]
ASF subversion and git services commented on SYNCOPE-1120:
--
Commit
On 23/06/2017 11:17, Colm O hEigeartaigh wrote:
On Fri, Jun 23, 2017 at 9:36 AM, Francesco Chicchiriccò
wrote:
+1 for the "Bearer" Authorization header proposal, more standards are
welcome :-)
Since we introduced JWT in 2.0.3, I am not sure whether it makes sense to
keep
On Fri, Jun 23, 2017 at 9:36 AM, Francesco Chicchiriccò wrote:
> +1 for the "Bearer" Authorization header proposal, more standards are
> welcome :-)
>
> Since we introduced JWT in 2.0.3, I am not sure whether it makes sense to
> keep supporting the X-Syncope-Token header
OK fair enough, here is the JIRA:
https://issues.apache.org/jira/browse/SYNCOPE-1120
How do we maintain the release notes?
Colm.
On Fri, Jun 23, 2017 at 10:34 AM, Francesco Chicchiriccò <
ilgro...@apache.org> wrote:
> On 23/06/2017 11:17, Colm O hEigeartaigh wrote:
>
>> On Fri, Jun 23, 2017
Colm O hEigeartaigh created SYNCOPE-1120:
Summary: Use the standard Bearer Authorization header for JWT
tokens
Key: SYNCOPE-1120
URL: https://issues.apache.org/jira/browse/SYNCOPE-1120
On 23/06/2017 12:14, Colm O hEigeartaigh wrote:
OK fair enough, here is the JIRA:
https://issues.apache.org/jira/browse/SYNCOPE-112
Thanks!
How do we maintain the release notes?
Not very efficiently ATM, I'd say: essentially, in the release process,
there are some steps where commits
Hi all,
Larry McCay from Apache Knox (amongst other projects) raised an interesting
point here:
https://twitter.com/lmccay/status/877981989638356992
Rather than use a custom header "X-Syncope-Token" to include the JWT token
when invoking on the Syncope REST services, we might as well instead
On 23/06/2017 10:34, Colm O hEigeartaigh wrote:
Hi all,
Larry McCay from Apache Knox (amongst other projects) raised an interesting
point here:
https://twitter.com/lmccay/status/877981989638356992
Rather than use a custom header "X-Syncope-Token" to include the JWT token
when invoking on the
[
https://issues.apache.org/jira/browse/SYNCOPE-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060819#comment-16060819
]
ASF subversion and git services commented on SYNCOPE-1119:
--
Commit
[
https://issues.apache.org/jira/browse/SYNCOPE-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060820#comment-16060820
]
ASF subversion and git services commented on SYNCOPE-1117:
--
Commit
[
https://issues.apache.org/jira/browse/SYNCOPE-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060822#comment-16060822
]
ASF subversion and git services commented on SYNCOPE-1119:
--
Commit
Andrea Patricelli created SYNCOPE-1122:
--
Summary: Enduser must show all attributes of custpom form has
empty section with show=true
Key: SYNCOPE-1122
URL: https://issues.apache.org/jira/browse/SYNCOPE-1122
[
https://issues.apache.org/jira/browse/SYNCOPE-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060847#comment-16060847
]
Francesco Chicchiriccò commented on SYNCOPE-1119:
-
Maybe the gmaven-plugin (we already
Colm O hEigeartaigh wrote:
> Hi all,
>
> I'm seeing an error with the installer on master, where I'm ending up with
> an invalid console pom.xml, as it's copying an extra "setupActivitiModeler"
> plugin. The code in the installer manually adds this plugin in
>
20 matches
Mail list logo