[jira] [Commented] (SYNCOPE-1178) PlainSchema page empty while self update on Enduser
[ https://issues.apache.org/jira/browse/SYNCOPE-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16110464#comment-16110464 ] ASF subversion and git services commented on SYNCOPE-1178: -- Commit 7ced59639e09e0343d410b8b28894fb8e4480c2d in syncope's branch refs/heads/2_0_X from [~skylark17] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=7ced596 ] [SYNCOPE-1178] PlainSchema page empty while self update on Enduser > PlainSchema page empty while self update on Enduser > > > Key: SYNCOPE-1178 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1178 > Project: Syncope > Issue Type: Bug > Components: core, enduser >Reporter: Andrea Patricelli >Assignee: Matteo Alessandroni > Fix For: 2.0.5, 2.1.0 > > > Sometimes, while updating an user, PlainSchema tab is empty and this also > leads test to fail. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (SYNCOPE-1171) Skip Relationships page when no relationships exist
[ https://issues.apache.org/jira/browse/SYNCOPE-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò closed SYNCOPE-1171. --- Resolution: Won't Fix > Skip Relationships page when no relationships exist > --- > > Key: SYNCOPE-1171 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1171 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Colm O hEigeartaigh >Priority: Trivial > Attachments: relationships.png > > > When creating a new user in the console, with no relationships defined, you > come to a page that says: > Relationships > No relationships defined > It would be better just to skip this page altogether if no relationships are > available. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SYNCOPE-1171) Skip Relationships page when no relationships exist
[ https://issues.apache.org/jira/browse/SYNCOPE-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16110412#comment-16110412 ] Francesco Chicchiriccò commented on SYNCOPE-1171: - That page also gives the possibility to add relationships (see attached screenshot), so it cannot be skipped. > Skip Relationships page when no relationships exist > --- > > Key: SYNCOPE-1171 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1171 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Colm O hEigeartaigh >Priority: Trivial > Fix For: 2.0.5, 2.1.0 > > Attachments: relationships.png > > > When creating a new user in the console, with no relationships defined, you > come to a page that says: > Relationships > No relationships defined > It would be better just to skip this page altogether if no relationships are > available. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SYNCOPE-1171) Skip Relationships page when no relationships exist
[ https://issues.apache.org/jira/browse/SYNCOPE-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1171: Attachment: relationships.png > Skip Relationships page when no relationships exist > --- > > Key: SYNCOPE-1171 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1171 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Colm O hEigeartaigh >Priority: Trivial > Fix For: 2.0.5, 2.1.0 > > Attachments: relationships.png > > > When creating a new user in the console, with no relationships defined, you > come to a page that says: > Relationships > No relationships defined > It would be better just to skip this page altogether if no relationships are > available. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SYNCOPE-1171) Skip Relationships page when no relationships exist
[ https://issues.apache.org/jira/browse/SYNCOPE-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1171: Fix Version/s: (was: 2.0.5) (was: 2.1.0) > Skip Relationships page when no relationships exist > --- > > Key: SYNCOPE-1171 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1171 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Colm O hEigeartaigh >Priority: Trivial > Attachments: relationships.png > > > When creating a new user in the console, with no relationships defined, you > come to a page that says: > Relationships > No relationships defined > It would be better just to skip this page altogether if no relationships are > available. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1177) Configuration Parameter deletion should ask for confirmation
[ https://issues.apache.org/jira/browse/SYNCOPE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-1177. - Resolution: Fixed > Configuration Parameter deletion should ask for confirmation > > > Key: SYNCOPE-1177 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1177 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 2.0.4 >Reporter: Andrea Patricelli >Assignee: Francesco Chicchiriccò >Priority: Minor > Fix For: 2.0.5, 2.1.0 > > > 1. Login into console > 2. Go to Configuration > Parameters > 3. click on a schema; a toggle menu will appear. Then delete a schema, You > will not be prompted to confirm deletion of such schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SYNCOPE-1178) PlainSchema page empty while self update on Enduser
[ https://issues.apache.org/jira/browse/SYNCOPE-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16110465#comment-16110465 ] ASF subversion and git services commented on SYNCOPE-1178: -- Commit 89fe8311579a2079c33a17cadbdb9be8e172972f in syncope's branch refs/heads/master from [~skylark17] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=89fe831 ] [SYNCOPE-1178] PlainSchema page empty while self update on Enduser > PlainSchema page empty while self update on Enduser > > > Key: SYNCOPE-1178 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1178 > Project: Syncope > Issue Type: Bug > Components: core, enduser >Reporter: Andrea Patricelli >Assignee: Matteo Alessandroni > Fix For: 2.0.5, 2.1.0 > > > Sometimes, while updating an user, PlainSchema tab is empty and this also > leads test to fail. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SYNCOPE-1177) Configuration Parameter deletion should ask for confirmation
[ https://issues.apache.org/jira/browse/SYNCOPE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16110450#comment-16110450 ] ASF subversion and git services commented on SYNCOPE-1177: -- Commit 7ea4eaa3815349d5b7f78b950fdf863fa55fb399 in syncope's branch refs/heads/2_0_X from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=7ea4eaa ] [SYNCOPE-1177] Confirmation flag for all ActionType.DELETE > Configuration Parameter deletion should ask for confirmation > > > Key: SYNCOPE-1177 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1177 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 2.0.4 >Reporter: Andrea Patricelli >Assignee: Francesco Chicchiriccò >Priority: Minor > Fix For: 2.0.5, 2.1.0 > > > 1. Login into console > 2. Go to Configuration > Parameters > 3. click on a schema; a toggle menu will appear. Then delete a schema, You > will not be prompted to confirm deletion of such schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SYNCOPE-1177) Configuration Parameter deletion should ask for confirmation
[ https://issues.apache.org/jira/browse/SYNCOPE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16110451#comment-16110451 ] ASF subversion and git services commented on SYNCOPE-1177: -- Commit 3948bbd7f6870fe50b06fefe1a2b26286544e777 in syncope's branch refs/heads/master from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=3948bbd ] [SYNCOPE-1177] Confirmation flag for all ActionType.DELETE > Configuration Parameter deletion should ask for confirmation > > > Key: SYNCOPE-1177 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1177 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 2.0.4 >Reporter: Andrea Patricelli >Assignee: Francesco Chicchiriccò >Priority: Minor > Fix For: 2.0.5, 2.1.0 > > > 1. Login into console > 2. Go to Configuration > Parameters > 3. click on a schema; a toggle menu will appear. Then delete a schema, You > will not be prompted to confirm deletion of such schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1177) Configuration Parameter deletion should ask for confirmation
[ https://issues.apache.org/jira/browse/SYNCOPE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò reassigned SYNCOPE-1177: --- Assignee: Francesco Chicchiriccò > Configuration Parameter deletion should ask for confirmation > > > Key: SYNCOPE-1177 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1177 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 2.0.4 >Reporter: Andrea Patricelli >Assignee: Francesco Chicchiriccò >Priority: Minor > Fix For: 2.0.5, 2.1.0 > > > 1. Login into console > 2. Go to Configuration > Parameters > 3. click on a schema; a toggle menu will appear. Then delete a schema, You > will not be prompted to confirm deletion of such schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1178) PlainSchema page empty while self update on Enduser
[ https://issues.apache.org/jira/browse/SYNCOPE-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1178. -- Resolution: Fixed > PlainSchema page empty while self update on Enduser > > > Key: SYNCOPE-1178 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1178 > Project: Syncope > Issue Type: Bug > Components: core, enduser >Reporter: Andrea Patricelli >Assignee: Matteo Alessandroni > Fix For: 2.0.5, 2.1.0 > > > Sometimes, while updating an user, PlainSchema tab is empty and this also > leads test to fail. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1155) Hard-coded /syncope-enduser HTTP subcontext
[
https://issues.apache.org/jira/browse/SYNCOPE-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matteo Alessandroni reassigned SYNCOPE-1155:
Assignee: Matteo Alessandroni
> Hard-coded /syncope-enduser HTTP subcontext
> ---
>
> Key: SYNCOPE-1155
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1155
> Project: Syncope
> Issue Type: Improvement
> Components: enduser
>Reporter: Francesco Chicchiriccò
>Assignee: Matteo Alessandroni
> Fix For: 2.0.5, 2.1.0
>
>
> Several files in the Enduser JS sources contain references like as follows:
> {code}
> any.getAuxClasses = function () {
> return $http.get("/syncope-enduser/api/auxClasses")
> .then(function (response) {
> return response.data;
> }, function (response) {
> console.error("Something went wrong during
> auxiliaryClasses retrieval, exit with status: ",
> response);
> return $q.reject(response.data ||
> response.statusText);
> });
> };
> {code}
> e.g. static references to {{/syncope-enduser}}.
> This would cause troubles when there is need to deploy the WAR file with a
> different name, or behind a reverse proxy.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (SYNCOPE-1177) Configuration Parameter deletion should ask for confirmation
[ https://issues.apache.org/jira/browse/SYNCOPE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1177: Summary: Configuration Parameter deletion should ask for confirmation (was: Schema Configuration deletion should ask for confirmation) > Configuration Parameter deletion should ask for confirmation > > > Key: SYNCOPE-1177 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1177 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 2.0.4 >Reporter: Andrea Patricelli >Priority: Minor > Fix For: 2.0.5, 2.1.0 > > > 1. Login into console > 2. Go to Configuration > Parameters > 3. click on a schema; a toggle menu will appear. Then delete a schema, You > will not be prompted to confirm deletion of such schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SYNCOPE-1183) Realm attribute available (as a detail) to use as a column in the "realm view" object list
[ https://issues.apache.org/jira/browse/SYNCOPE-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1183: Component/s: console > Realm attribute available (as a detail) to use as a column in the "realm > view" object list > -- > > Key: SYNCOPE-1183 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1183 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Filipe Silva >Priority: Trivial > Fix For: 2.0.5, 2.1.0 > > > Hi > I have to create a derived schema for each AnyType (with realm as the > Expression) in syncope to be able to provide in the realm object list that > information (very useful if in a parent realm). > I would suggest to have that info available as a detail in the column list > for use. > Thanks > Filipe Silva -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SYNCOPE-1183) Realm attribute available (as a detail) to use as a column in the "realm view" object list
Filipe Silva created SYNCOPE-1183: - Summary: Realm attribute available (as a detail) to use as a column in the "realm view" object list Key: SYNCOPE-1183 URL: https://issues.apache.org/jira/browse/SYNCOPE-1183 Project: Syncope Issue Type: Improvement Reporter: Filipe Silva Priority: Trivial Hi I have to create a derived schema for each AnyType (with realm as the Expression) in syncope to be able to provide in the realm object list that information (very useful if in a parent realm). I would suggest to have that info available as a detail in the column list for use. Thanks Filipe Silva -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SYNCOPE-1183) Realm attribute available (as a detail) to use as a column in the "realm view" object list
[ https://issues.apache.org/jira/browse/SYNCOPE-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1183: Fix Version/s: 2.1.0 2.0.5 > Realm attribute available (as a detail) to use as a column in the "realm > view" object list > -- > > Key: SYNCOPE-1183 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1183 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Filipe Silva >Priority: Trivial > Fix For: 2.0.5, 2.1.0 > > > Hi > I have to create a derived schema for each AnyType (with realm as the > Expression) in syncope to be able to provide in the realm object list that > information (very useful if in a parent realm). > I would suggest to have that info available as a detail in the column list > for use. > Thanks > Filipe Silva -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SYNCOPE-1155) Hard-coded /syncope-enduser HTTP subcontext
[
https://issues.apache.org/jira/browse/SYNCOPE-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16110766#comment-16110766
]
ASF subversion and git services commented on SYNCOPE-1155:
--
Commit 0a0bf05c42a6ef59835c3e247035cc898ab4c4db in syncope's branch
refs/heads/2_0_X from [~skylark17]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=0a0bf05 ]
[SYNCOPE-1155] Hard-coded /syncope-enduser HTTP subcontext
> Hard-coded /syncope-enduser HTTP subcontext
> ---
>
> Key: SYNCOPE-1155
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1155
> Project: Syncope
> Issue Type: Improvement
> Components: enduser
>Reporter: Francesco Chicchiriccò
>Assignee: Matteo Alessandroni
> Fix For: 2.0.5, 2.1.0
>
>
> Several files in the Enduser JS sources contain references like as follows:
> {code}
> any.getAuxClasses = function () {
> return $http.get("/syncope-enduser/api/auxClasses")
> .then(function (response) {
> return response.data;
> }, function (response) {
> console.error("Something went wrong during
> auxiliaryClasses retrieval, exit with status: ",
> response);
> return $q.reject(response.data ||
> response.statusText);
> });
> };
> {code}
> e.g. static references to {{/syncope-enduser}}.
> This would cause troubles when there is need to deploy the WAR file with a
> different name, or behind a reverse proxy.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SYNCOPE-1183) Realm attribute available (as a detail) to use as a column in the "realm view" object list
[ https://issues.apache.org/jira/browse/SYNCOPE-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16111015#comment-16111015 ] ASF subversion and git services commented on SYNCOPE-1183: -- Commit e1a9e9e7f66335247d0b21722bce72cc07cfd296 in syncope's branch refs/heads/2_0_X from [~skylark17] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=e1a9e9e ] [SYNCOPE-1183] 'realm' attribute is now added as a default column in 'Realms' view > Realm attribute available (as a detail) to use as a column in the "realm > view" object list > -- > > Key: SYNCOPE-1183 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1183 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Filipe Silva >Assignee: Matteo Alessandroni >Priority: Trivial > Fix For: 2.0.5, 2.1.0 > > > Hi > I have to create a derived schema for each AnyType (with realm as the > Expression) in syncope to be able to provide in the realm object list that > information (very useful if in a parent realm). > I would suggest to have that info available as a detail in the column list > for use. > Thanks > Filipe Silva -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SYNCOPE-1183) Realm attribute available (as a detail) to use as a column in the "realm view" object list
[ https://issues.apache.org/jira/browse/SYNCOPE-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16111017#comment-16111017 ] ASF subversion and git services commented on SYNCOPE-1183: -- Commit bfce0046e7e278d0fd66ceb939a01ac056f89be8 in syncope's branch refs/heads/master from [~skylark17] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=bfce004 ] [SYNCOPE-1183] 'realm' attribute is now added as a default column in 'Realms' view > Realm attribute available (as a detail) to use as a column in the "realm > view" object list > -- > > Key: SYNCOPE-1183 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1183 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Filipe Silva >Assignee: Matteo Alessandroni >Priority: Trivial > Fix For: 2.0.5, 2.1.0 > > > Hi > I have to create a derived schema for each AnyType (with realm as the > Expression) in syncope to be able to provide in the realm object list that > information (very useful if in a parent realm). > I would suggest to have that info available as a detail in the column list > for use. > Thanks > Filipe Silva -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1161) Option to clone a resource
[ https://issues.apache.org/jira/browse/SYNCOPE-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reassigned SYNCOPE-1161: Assignee: Matteo Alessandroni > Option to clone a resource > -- > > Key: SYNCOPE-1161 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1161 > Project: Syncope > Issue Type: Wish > Components: console >Affects Versions: 2.0.4 >Reporter: Filipe Silva >Assignee: Matteo Alessandroni >Priority: Minor > Fix For: 2.0.5, 2.1.0 > > > Sometimes we need to create a new resource in a connector based in a previous > one (for instance to separate the provision types) an option to clone the > resource would be nice -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1183) Realm attribute available (as a detail) to use as a column in the "realm view" object list
[ https://issues.apache.org/jira/browse/SYNCOPE-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1183. -- Resolution: Fixed > Realm attribute available (as a detail) to use as a column in the "realm > view" object list > -- > > Key: SYNCOPE-1183 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1183 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Filipe Silva >Assignee: Matteo Alessandroni >Priority: Trivial > Fix For: 2.0.5, 2.1.0 > > > Hi > I have to create a derived schema for each AnyType (with realm as the > Expression) in syncope to be able to provide in the realm object list that > information (very useful if in a parent realm). > I would suggest to have that info available as a detail in the column list > for use. > Thanks > Filipe Silva -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SYNCOPE-1155) Hard-coded /syncope-enduser HTTP subcontext
[
https://issues.apache.org/jira/browse/SYNCOPE-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16110768#comment-16110768
]
ASF subversion and git services commented on SYNCOPE-1155:
--
Commit cb9e145396d2ae54fe4f37110675dc84bc7c9c32 in syncope's branch
refs/heads/master from [~skylark17]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=cb9e145 ]
[SYNCOPE-1155] Hard-coded /syncope-enduser HTTP subcontext
> Hard-coded /syncope-enduser HTTP subcontext
> ---
>
> Key: SYNCOPE-1155
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1155
> Project: Syncope
> Issue Type: Improvement
> Components: enduser
>Reporter: Francesco Chicchiriccò
>Assignee: Matteo Alessandroni
> Fix For: 2.0.5, 2.1.0
>
>
> Several files in the Enduser JS sources contain references like as follows:
> {code}
> any.getAuxClasses = function () {
> return $http.get("/syncope-enduser/api/auxClasses")
> .then(function (response) {
> return response.data;
> }, function (response) {
> console.error("Something went wrong during
> auxiliaryClasses retrieval, exit with status: ",
> response);
> return $q.reject(response.data ||
> response.statusText);
> });
> };
> {code}
> e.g. static references to {{/syncope-enduser}}.
> This would cause troubles when there is need to deploy the WAR file with a
> different name, or behind a reverse proxy.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1155) Hard-coded /syncope-enduser HTTP subcontext
[
https://issues.apache.org/jira/browse/SYNCOPE-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matteo Alessandroni resolved SYNCOPE-1155.
--
Resolution: Fixed
> Hard-coded /syncope-enduser HTTP subcontext
> ---
>
> Key: SYNCOPE-1155
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1155
> Project: Syncope
> Issue Type: Improvement
> Components: enduser
>Reporter: Francesco Chicchiriccò
>Assignee: Matteo Alessandroni
> Fix For: 2.0.5, 2.1.0
>
>
> Several files in the Enduser JS sources contain references like as follows:
> {code}
> any.getAuxClasses = function () {
> return $http.get("/syncope-enduser/api/auxClasses")
> .then(function (response) {
> return response.data;
> }, function (response) {
> console.error("Something went wrong during
> auxiliaryClasses retrieval, exit with status: ",
> response);
> return $q.reject(response.data ||
> response.statusText);
> });
> };
> {code}
> e.g. static references to {{/syncope-enduser}}.
> This would cause troubles when there is need to deploy the WAR file with a
> different name, or behind a reverse proxy.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SYNCOPE-1171) Skip Relationships page when no relationships exist
[ https://issues.apache.org/jira/browse/SYNCOPE-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16111339#comment-16111339 ] Colm O hEigeartaigh commented on SYNCOPE-1171: -- What I meant here was to skip the page if no relationship types are defined in syncope. The "+" button is meaningless in this context, as you can't create a relationship anyway if there are no types available. Not a big deal either way though :-) > Skip Relationships page when no relationships exist > --- > > Key: SYNCOPE-1171 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1171 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Colm O hEigeartaigh >Priority: Trivial > Attachments: relationships.png > > > When creating a new user in the console, with no relationships defined, you > come to a page that says: > Relationships > No relationships defined > It would be better just to skip this page altogether if no relationships are > available. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
