On 25/07/2018 20:58, Wyllys Ingersoll wrote:
When I create a user with a role that has all of the entitlements and
attempt to login to the console, it fails and this error is in the
console.log:
Hi,
the log below is not very explicative, it is hard to guess the actual
problem: maybe you have
When I create a user with a role that has all of the entitlements and
attempt to login to the console, it fails and this error is in the
console.log:
18:52:24.186 ERROR
org.apache.syncope.client.console.SyncopeConsoleRequestCycleListener -
Exception found
org.apache.wicket.WicketRuntimeException:
On 24/07/2018 15:03, Wyllys Ingersoll wrote:
Thanks, I got it to work by giving my "Admin" role a subset of the
complete list of entitlements.
It seems that granting the entire list of entitlements to a role or a
user makes it unauthorized to access the UI, which is
counter-intuitive, IMO.
Thanks, I got it to work by giving my "Admin" role a subset of the
complete list of entitlements.
It seems that granting the entire list of entitlements to a role or a
user makes it unauthorized to access the UI, which is
counter-intuitive, IMO.
Its also not clear what entitlements are in effect
On 23/07/2018 22:59, Wyllys Ingersoll wrote:
Using the 2.1.1-SNAPSHOT build, I am now able to login to the 2nd
domain as the default "admin" account, but I cannot login using any
other accounts even if those accounts are assigned a role with all of
the privileges.
You can see the same error on
Using the 2.1.1-SNAPSHOT build, I am now able to login to the 2nd
domain as the default "admin" account, but I cannot login using any
other accounts even if those accounts are assigned a role with all of
the privileges.
You can see the same error on the demo vm using login
"testadm/password2" in
Done - https://issues.apache.org/jira/browse/SYNCOPE-1342
thanks for confirming this, I thought I was just doing something
stupid or the documentation was missing a step or 2.
On Sun, Jul 22, 2018 at 1:25 PM, Francesco Chicchiriccò
wrote:
> Hi,
> I have replicated your Docker-based setup, with
Hi,
I have replicated your Docker-based setup, with two domains and
2.1.1-SNAPSHOT, found the same issue.
...that could be easily replicated by attempting to log in on the public
demo:
http://syncope-vm.apache.org:9080/syncope-console
on the Two domain, with credentials admin / password2 -
I created a role in the 2nd domain and granted it all of the
entitlements using the REST api, then assigned that role to a user
("admin2") in the 2nd domain. Now when I attempt to login to the 2nd
domain on the console UI, I get the following errors in the core.log
file:
Its basically
The reason it was reverting back to the Master domain was due to the
browser automatically re-populating the fields, I've fixed that issue
but still cannot login to the 2nd domain.
I have verified that the password is correct and I can get a token
using the /rest/accessTokens API with the 2nd
On 21/07/2018 13:44, Wyllys Ingersoll wrote:
I followed the guide and have setup using the docker containers from
docker-hub apache/syncope, not maven.
I setup a 2nd database and redeployed the core and the console apps.
Now I ca see the new domain when I query the /rest/domains endpoint.
At
I followed the guide and have setup using the docker containers from
docker-hub apache/syncope, not maven.
I setup a 2nd database and redeployed the core and the console apps.
Now I ca see the new domain when I query the /rest/domains endpoint.
At this point I can even login to the new domain
On 20/07/2018 19:15, Wyllys Ingersoll wrote:
Im trying to get multiple domains configured in Syncope 2.1.0, I've
read the docs and have created a 2nd set of files under the "domains"
directory and the system seems to recognize them and connects to their
DB.
I was able to add the domain
13 matches
Mail list logo
