For the records, here's how the conversation should have appeared.
HTH
Regards.
On 28/09/2016 17:26, Matteo Di Carlo wrote:
Hi,
I am exploring the option of assigning the realm to the syncope end-user via
self registration.
Found that "Realm" field has been disabled under "Groups" tab of self
registration.
Kindly let us know the reason behind disabling the "Realm" field, Also please let us
know how to enable this "Realm" field.
Hi Sitaram,
Realm field is actually disabled, and stubbed to allow a free customization of
the enduser, particularly to let you decide when to use realms or not.
As you can see in [1] (SYNCOPE-952), we need first to resolve the issue to
retrieve all existing realms. Anyway javascript side you can enable the realm
choice through the following 2 steps:
-First, in user-groups.html switch ng-disabled of the realm label to "true" .
(line 32)
-Then, in UserController.js replace entirely the initRealms() method with the
following one:
var initRealms = function () {
RealmService.getAvailableRealms().then(function (response) {
for (var i in response) {
$scope.availableRealms.push(response[i].name);
}
});
};
As I specified you will not be able to retrieve all existing realms.
So, since the realm management is mocked javascript side, initRealms() will not
work till SYNCOPE-952 isn't resolved. In the meantime you could simulate the
service passing to $scope.availableRealms a static list of realms.
[1] https://issues.apache.org/jira/browse/SYNCOPE-952
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/
