Mike
The overall workflow that you are attempting to achieve is not possible
without customizing OWF - there is no configuration that allows the OWF
container to send special data such as the authentication ticket to all
launched widgets.
For simply trying to get OWF itself to authenticate against your web service,
it looks like your example XML has some redundancy. The authenticationManager
bean definition is not necessary since you have the <authentication-manager>
element. Beyond that, I would have to see the code of your
ozone.securitysample.authentication.rest.WebServiceAuthenticationProvider
class to see where any problems are.
Are you seeing a specific stacktrace or other error?
Ross Pokorny
On Tuesday, May 31, 2016 9:43:25 AM EDT Mike Lanciano wrote:
> I am having trouble implementing and even understanding if what I am
> attempting to achieve is possible. Here is what I want to accomplish:
>
> 1. User Logs in to OWF
> 2. Credentials are verified against a RESTful Auth Service
> 3. If valid, the Auth Service returns a Token
> 4. Token is made accessible to widgets which can then inject it to their
> own calls
> 5. If widget receives a notification to reauthenticate it notifies OWF and
> OWF will mark the current session expired and ask the user to reauth.
>
> I figured I would attempt to get OWF to Auth against a web service as the
> first step. Below is what I tried.