-
1. Re: errai.require_authentication_for_all
cbrock Sep 3, 2010 1:13 PM (in response to umk)In order for there to be an authentication challenge, and actual security client needs to be configured. You must also have configured a security adapter, such as the JAAS adapter. You can look at our "TheStore" demo for an example of this fully configured.
-
2. Re: errai.require_authentication_for_all
umk Sep 4, 2010 11:20 PM (in response to cbrock)A security adapter is configured for the HelloWorld application (sandbox-archetype):
errai.authentication_adapter=org.jboss.errai.bus.server.security.auth.JAASAdapter
TheStore appears to rely on Errai Workspaces for authentication. I guess I was wondering if authentication could be used with other applications without requiring them to be Errai Workspaces. If so, can this be achieved without too much difficultly? Thanks.
-
3. Re: errai.require_authentication_for_all
jdestef Oct 5, 2010 10:15 PM (in response to umk)Hi,
Did you ever figure out if this could be done without using the Workspace?
Thx
-
4. Re: errai.require_authentication_for_all
umk Oct 6, 2010 8:27 AM (in response to jdestef)Nope. I was hoping to hear back from Christopher after my last message... If I find a way to do this, I'll post back here. Maybe you can do the same??
-
5. Re: errai.require_authentication_for_all
jdestef Oct 6, 2010 9:32 AM (in response to umk)Will do.
Thx
-
6. Re: errai.require_authentication_for_all
cbrock Oct 8, 2010 2:18 PM (in response to jdestef)Okay, the JAASAdapter is not tied to workspace. Rather, it relies on their being an authentication client on the clientside bus to communicate with it. We have really only implemented on in Workspaces, and we should really be documenting the protocol so people can implement their own authentication clients.
Essentially is uses a standard messaging protocol to communicate back and forth. That protocol can be implemented by a custom client, which was really the idea.