[jira] [Created] (SYNCOPE-1035) JWT-based access to REST services
Francesco Chicchiriccò created SYNCOPE-1035: --- Summary: JWT-based access to REST services Key: SYNCOPE-1035 URL: https://issues.apache.org/jira/browse/SYNCOPE-1035 Project: Syncope Issue Type: New Feature Components: client, console, core Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 2.0.3, 2.1.0 Since the beginning, access to the REST services is protected via Basic Authentication, with credentials sent along each and every request. As improvement, we can switch to an architecture where there is an explicit REST service for obtaining some sort of token (requiring credentials) and then all other REST services can be accessed by sending along such token instead of credentials. This will ease future works for enabling SSO via SAML, OAuth 2.0 or other standards. About the token format, it seems that [JSON Web Tokens|https://jwt.io/] are quite the default choice, especially considering the support that CXF already provides for that. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SYNCOPE-1018) Social registration for Enduser UI
[ https://issues.apache.org/jira/browse/SYNCOPE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15888132#comment-15888132 ] Govinda Malavipathirana commented on SYNCOPE-1018: -- Hi Mr.Andrea, Thanks for the guidance. I will look into it. Sincerely, Govinda. > Social registration for Enduser UI > -- > > Key: SYNCOPE-1018 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1018 > Project: Syncope > Issue Type: New Feature > Components: enduser >Reporter: Francesco Chicchiriccò > Labels: gsoc2017 > Fix For: 2.1.0 > > > Provide an optional feature, to exploit for self-registration via Enduser UI, > which allows to take the initial values for some attributes in Syncope from a > profile owned by the registering user in one of most popular social networks > as Twitter, LinkedIn, Facebook, Google+, ... -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (SYNCOPE-1029) Change modal window title and button bars background
[
https://issues.apache.org/jira/browse/SYNCOPE-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabio martelli reassigned SYNCOPE-1029:
---
Assignee: fabio martelli
> Change modal window title and button bars background
>
>
> Key: SYNCOPE-1029
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1029
> Project: Syncope
> Issue Type: Improvement
> Components: console
>Affects Versions: 2.0.2
>Reporter: Francesco Chicchiriccò
>Assignee: fabio martelli
> Fix For: 2.0.3, 2.1.0
>
>
> The title (top) and button (bottom) bars of modal windows in Admin Console
> are currently set with a white background, as the body.
> Other popular applications - as JIRA, for example - use some light grey
> background {{#f0f0f0}} instead, which improves usability.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SYNCOPE-1018) Social registration for Enduser UI
[ https://issues.apache.org/jira/browse/SYNCOPE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15887989#comment-15887989 ] Andrea Patricelli commented on SYNCOPE-1018: HI Govinda, first of all I suggest to check if your environment respects prerequisites to run Syncope. Please take a look at [1]. There you'll also find some useful documentation about Syncope (getting started, repo url, etc.). Moreover you should be able to run Syncope because develoment must be done starting from Syncope code and on its Enduser (developed in AngularJS). Your sample JEE application could be an initial approach to the problem, useful to understand all "ingredients" needed, but I suggest you to move ASAP to Syncope code and try to undestand how to implement the flow on the Enduser project. [1] https://syncope.apache.org/building.html#Prerequisites > Social registration for Enduser UI > -- > > Key: SYNCOPE-1018 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1018 > Project: Syncope > Issue Type: New Feature > Components: enduser >Reporter: Francesco Chicchiriccò > Labels: gsoc2017 > Fix For: 2.1.0 > > > Provide an optional feature, to exploit for self-registration via Enduser UI, > which allows to take the initial values for some attributes in Syncope from a > profile owned by the registering user in one of most popular social networks > as Twitter, LinkedIn, Facebook, Google+, ... -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SYNCOPE-1018) Social registration for Enduser UI
[ https://issues.apache.org/jira/browse/SYNCOPE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15887949#comment-15887949 ] Govinda Malavipathirana commented on SYNCOPE-1018: -- Hi Mr Andrea, I went through the document and tried to install Apache Syncope to my machine but hadn't any luck. So I created a sample J2EE page and trying to implement login session through the facebook. So could you give me a advice what should I do next? Current progress I will give you an update within tomorrow (the login through facebook). Sincerely, Govinda > Social registration for Enduser UI > -- > > Key: SYNCOPE-1018 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1018 > Project: Syncope > Issue Type: New Feature > Components: enduser >Reporter: Francesco Chicchiriccò > Labels: gsoc2017 > Fix For: 2.1.0 > > > Provide an optional feature, to exploit for self-registration via Enduser UI, > which allows to take the initial values for some attributes in Syncope from a > profile owned by the registering user in one of most popular social networks > as Twitter, LinkedIn, Facebook, Google+, ... -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SYNCOPE-1027) Mapping errors cannot be fixed when defining provision rules for a new resource
[
https://issues.apache.org/jira/browse/SYNCOPE-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabio martelli resolved SYNCOPE-1027.
-
Resolution: Fixed
> Mapping errors cannot be fixed when defining provision rules for a new
> resource
> ---
>
> Key: SYNCOPE-1027
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1027
> Project: Syncope
> Issue Type: Bug
> Components: console
>Affects Versions: 2.0.2
>Reporter: Francesco Chicchiriccò
>Assignee: fabio martelli
> Fix For: 2.0.3, 2.1.0
>
>
> How to replicate, from Admin Console:
> # from Topology, create new resource
> # once created, edit provision rules
> # create mapping for {{USER}}, add a single item without flagging {{Remote
> Key}}
> # once finished, click {{Save}}: an error message will appear: {{USER: There
> must be exactly one Remote Key}}
> # go back editing the mapping for {{USER}}, flag {{Remote Key}} for the only
> item available
> # click {{Save}} again: the same error message will appear again
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SYNCOPE-1027) Mapping errors cannot be fixed when defining provision rules for a new resource
[
https://issues.apache.org/jira/browse/SYNCOPE-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15887853#comment-15887853
]
ASF subversion and git services commented on SYNCOPE-1027:
--
Commit ad34459063e2959e9aecd5a6f795839946c7cc89 in syncope's branch
refs/heads/2_0_X from [~fmartelli]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=ad34459 ]
[SYNCOPE-1027] improve provision mappings management from administration console
> Mapping errors cannot be fixed when defining provision rules for a new
> resource
> ---
>
> Key: SYNCOPE-1027
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1027
> Project: Syncope
> Issue Type: Bug
> Components: console
>Affects Versions: 2.0.2
>Reporter: Francesco Chicchiriccò
>Assignee: fabio martelli
> Fix For: 2.0.3, 2.1.0
>
>
> How to replicate, from Admin Console:
> # from Topology, create new resource
> # once created, edit provision rules
> # create mapping for {{USER}}, add a single item without flagging {{Remote
> Key}}
> # once finished, click {{Save}}: an error message will appear: {{USER: There
> must be exactly one Remote Key}}
> # go back editing the mapping for {{USER}}, flag {{Remote Key}} for the only
> item available
> # click {{Save}} again: the same error message will appear again
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SYNCOPE-1027) Mapping errors cannot be fixed when defining provision rules for a new resource
[
https://issues.apache.org/jira/browse/SYNCOPE-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15887854#comment-15887854
]
ASF subversion and git services commented on SYNCOPE-1027:
--
Commit f46891466bc516551b62e284108af357012b7052 in syncope's branch
refs/heads/master from [~fmartelli]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=f468914 ]
[SYNCOPE-1027] improve provision mappings management from administration console
> Mapping errors cannot be fixed when defining provision rules for a new
> resource
> ---
>
> Key: SYNCOPE-1027
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1027
> Project: Syncope
> Issue Type: Bug
> Components: console
>Affects Versions: 2.0.2
>Reporter: Francesco Chicchiriccò
>Assignee: fabio martelli
> Fix For: 2.0.3, 2.1.0
>
>
> How to replicate, from Admin Console:
> # from Topology, create new resource
> # once created, edit provision rules
> # create mapping for {{USER}}, add a single item without flagging {{Remote
> Key}}
> # once finished, click {{Save}}: an error message will appear: {{USER: There
> must be exactly one Remote Key}}
> # go back editing the mapping for {{USER}}, flag {{Remote Key}} for the only
> item available
> # click {{Save}} again: the same error message will appear again
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SYNCOPE-1018) Social registration for Enduser UI
[ https://issues.apache.org/jira/browse/SYNCOPE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15887599#comment-15887599 ] Govinda Malavipathirana commented on SYNCOPE-1018: -- Hi Andrea, Thanks for the fast reply. I will look into to this and come up with ideas. Thank you > Social registration for Enduser UI > -- > > Key: SYNCOPE-1018 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1018 > Project: Syncope > Issue Type: New Feature > Components: enduser >Reporter: Francesco Chicchiriccò > Labels: gsoc2017 > Fix For: 2.1.0 > > > Provide an optional feature, to exploit for self-registration via Enduser UI, > which allows to take the initial values for some attributes in Syncope from a > profile owned by the registering user in one of most popular social networks > as Twitter, LinkedIn, Facebook, Google+, ... -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (SYNCOPE-1027) Mapping errors cannot be fixed when defining provision rules for a new resource
[
https://issues.apache.org/jira/browse/SYNCOPE-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabio martelli reassigned SYNCOPE-1027:
---
Assignee: fabio martelli
> Mapping errors cannot be fixed when defining provision rules for a new
> resource
> ---
>
> Key: SYNCOPE-1027
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1027
> Project: Syncope
> Issue Type: Bug
> Components: console
>Affects Versions: 2.0.2
>Reporter: Francesco Chicchiriccò
>Assignee: fabio martelli
> Fix For: 2.0.3, 2.1.0
>
>
> How to replicate, from Admin Console:
> # from Topology, create new resource
> # once created, edit provision rules
> # create mapping for {{USER}}, add a single item without flagging {{Remote
> Key}}
> # once finished, click {{Save}}: an error message will appear: {{USER: There
> must be exactly one Remote Key}}
> # go back editing the mapping for {{USER}}, flag {{Remote Key}} for the only
> item available
> # click {{Save}} again: the same error message will appear again
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (SYNCOPE-1034) Assigned Auxiliary classes disappear in the Type Extensions panel when click on cancel
Marco Di Sabatino Di Diodoro created SYNCOPE-1034: - Summary: Assigned Auxiliary classes disappear in the Type Extensions panel when click on cancel Key: SYNCOPE-1034 URL: https://issues.apache.org/jira/browse/SYNCOPE-1034 Project: Syncope Issue Type: Bug Components: console Affects Versions: 2.0.2 Reporter: Marco Di Sabatino Di Diodoro Priority: Minor Fix For: 2.0.3, 2.1.0 Assigned Auxiliary classes disappear in the Type Extensions panel when click on cancel: 1) Edit an existing type extension with an associated class. 2) Edit Auxiliary classes assignment. 3) Click on cancel. If you refresh the view, the auxiliary classes are still present. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SYNCOPE-1018) Social registration for Enduser UI
[ https://issues.apache.org/jira/browse/SYNCOPE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15887521#comment-15887521 ] Andrea Patricelli commented on SYNCOPE-1018: Hi Govinda, Nice to meet you and glad to hear that you want to contribute :) Currently we haven't a social login mechanism in Enduser, though I think that the issue is a bit different. The goal of the issue is to provide a feature that allows social registration, that is the possibility to register (create an account) on Syncope through social network, taking some (basic) information directly from the social network and filling some fields (if present). The most common examples of interesting fields could be the mail or the firstname, etc. A further improvement could also be social-login to the self update section of the enduser, but this requires to work also on core module, the community is currently discussing about this and I do not exclude that something could be developed in the next months. BTW I suggest you to start reading the reference guide at [1] to better understand what Enduser is and what is the aim of this module. Best regards, Andrea [1] https://syncope.apache.org/docs/reference-guide.html#enduser-application > Social registration for Enduser UI > -- > > Key: SYNCOPE-1018 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1018 > Project: Syncope > Issue Type: New Feature > Components: enduser >Reporter: Francesco Chicchiriccò > Labels: gsoc2017 > Fix For: 2.1.0 > > > Provide an optional feature, to exploit for self-registration via Enduser UI, > which allows to take the initial values for some attributes in Syncope from a > profile owned by the registering user in one of most popular social networks > as Twitter, LinkedIn, Facebook, Google+, ... -- This message was sent by Atlassian JIRA (v6.3.15#6346)
