Pike1212
Since widgets are typically separate web applications from OWF, they typically
have their own authentication mechanisms. To avoid forcing the user to
authenticate to each widget separately from OWF, we recommend that you
configure OWF and your widgets to use a common authentication mechanism, such
as a single-sign-on solution or client side certificates. For example, the
default security configuration for OWF allows it to interact with a CAS server
(a single-sign-on system). When a user accesses OWF, they are redirected to
CAS, and log in there. Then OWF communicates with the CAS server in order to
validate that the user is logged in with a given identity. You could write
your widgets to also depend on CAS for authentication. That way, the user
will already be logged in once your widgets load, and your widgets will be
able to retrieve the user's information from CAS.
Ross Pokorny
OWF Community Support Team