22.12.2012 Views

Front cover - IBM Redbooks

Front cover - IBM Redbooks

Front cover - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

14.7 Summary<br />

632 Lotus Security Handbook<br />

com.ibm.websphere.security.auth.module.proxy.WSLoginModuleProxy<br />

required delegate=com.ibm.wps.sso.UserIdPasswordLoginModule;<br />

com.ibm.websphere.security.auth.module.proxy.WSLoginModuleProxy<br />

required delegate=com.ibm.wps.sso.UserIdPrincipalLoginModule;<br />

com.ibm.websphere.security.auth.module.proxy.WSLoginModuleProxy<br />

required delegate=com.ibm.wps.sso.PasswordCredentialLoginModule;<br />

com.ibm.websphere.security.auth.module.proxy.WSLoginModuleProxy<br />

required delegate=com.ibm.wps.sso.LTPATokenLoginModule;<br />

com.ibm.websphere.security.auth.module.proxy.WSLoginModuleProxy<br />

required delegate=com.tivoli.mts.PDLoginModule;<br />

};<br />

WpsSubjectExists {<br />

com.ibm.websphere.security.auth.module.proxy.WSLoginModuleProxy<br />

required delegate=com.ibm.wps.sso.GetCORBACredentialLoginModule;<br />

com.ibm.websphere.security.auth.module.proxy.WSLoginModuleProxy<br />

required delegate=com.ibm.wps.sso.CORBACredentialLoginModule;<br />

com.ibm.websphere.security.auth.module.proxy.WSLoginModuleProxy<br />

required delegate=com.ibm.wps.sso.LTPATokenLoginModule;<br />

com.ibm.websphere.security.auth.module.proxy.WSLoginModuleProxy<br />

required delegate=com.tivoli.mts.PDLoginModule;<br />

};<br />

After these steps are completed, the entire collaborative environment built during<br />

this chapter will be properly secured behind the new Tivoli Access Manager<br />

security service (via the WebSphere Edge Server plug-in) in terms of<br />

authentication.<br />

However, in our scenario the individual applications (that is, WebSphere Portal,<br />

Lotus Domino, and so forth) continue to handle basic “authorization.” That is,<br />

they check their own ACLs to verify if a user, as authenticated by TAM, actually<br />

has access to a given resource. TAM can also be utilized to provide centralized<br />

control over authorization in addition to authentication, but that is beyond the<br />

scope of this scenario and this Redbook.<br />

In this chapter we have shown the actual procedures utilized by the Redbook<br />

team to implement the <strong>Redbooks</strong>Co “secure collaboration” scenario in the<br />

<strong>Redbooks</strong> test lab. These procedures can be used as a starting point for<br />

implementing a similar scenario in your own environment.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!