Software as a Service: Enforcing role based access control using WebSphere Portal Server & Tivoli Directory Server

See how WebSphere portal access control features can be exploited for enforcing security in a SaaS application by restricting the set of portal pages and portlets that a particular user can access, based on the role of the user.

Mary Taylor (marytaylor@us.ibm.com), Senior IT Architect, IBM

Author Photo: Mary TaylorMary Taylor is a senior software engineer. She is working in the Strategic Technology Architecture and Incubation team, and she is currently working on an SOA CBS pilot. Her interests include DB2 and DataStage.



26 September 2007

See how WebSphere® Portal access control features can be exploited for enforcing security in a SaaS application by restricting the set of portal pages and portlets that a particular user can access, based on the role of the user.

System requirements

You'll need JavaScript™ enabled in your browser.

Transcript

Get the demo transcript (16KB).

Sample implementation artifact for building SaaS solutions on IBM middleware

A code snippet from a WebSphere Portal Server XML access script. This code sample shows a mapping of the editor role for the SaasBankInterestRatesCustomerPortlet to the LDAP group in the sample banking application: cn=wpsadmins,cn=groups,dc=bank1,dc=com

Duration

Less than 10 minutes.

Resources

Learn

Get products and technologies

  • Download IBM product evaluation versions and get your hands on application development tools and middleware products from DB2®, Lotus®, Rational®, Tivoli®, and WebSphere®.

Discuss

static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=WebSphere
ArticleID=324603
SummaryTitle=Software as a Service: Enforcing role based access control using WebSphere Portal Server & Tivoli Directory Server
publish-date=09262007