Websphere Portal 6.1

[unitas99007]

We've got our portal installation up and running, but I have two quick questions that need to be answered before we hand it over to the business side of things for review / approval.

1) In Tools 8.94 / Websphere 5.02 there was a documented way to "passthrough" credentials so that a JDE user could log into the Portal with the JDE credentials, not portal user credentials. Is this still supported? We don't want to have to create LDAP accounts for a bunch of people that are hourly just so they can log into the portal for employee self service.

2) Is there a way to enforce password expiration on Websphere Portal 6.1 without syncing Active Directory or Tivoli? It looks like we can create a user in the portal, but I don't see a configuration option for "password expires every x days" or "must be x number of characters".

We're currently running Websphere Portal 6.1.0.2 with the JDEdwards Collaborative Portal component installed. We're running JD Edwards 9.0 with the 8.98.2.4 tools release.

Any thoughts are very helpful. Thanks!

Unitas99007

 

[markdcci]

This may not directly answer your question and I hope it doesn't derail your thread, but we had the same problems and solved them in a different way.

We ran HR self service in Xe and used the old "owportal" due to its simplicity until our recent 9.0 upgrade. The old owportal was deprecated in 8.10. Therefore, like you we also got the WAS portal up and running for our dev environment during our upgrade. All of the setup, security and infrastructure required for simple HR self service functions was overkill. Therefore, we used what Oracle/JDE refers to as parameterized URL's to link to our existing SharePoint instance We threw together a very simple Sharepoint page with parameterized links back to specific JDE applications (e.g., a Sharepoint link that says "Timesheet Entry" that opens up the self service timesheet application directly, not the E1 menu). You have to log into E1 after you click the link and before it will open, but at least there is not another set of security involved. And as long as you have the browser window open the password is cached and you don't have to re-enter it on subsequent clicks to other links.

It's not perfect but it's much simpler than running WAS portal. If you don't have some type of portal running, such as SharePoint or similar, you could probably put together a simple ASP page with the links on it.

Hope this helps.

E1 - 9.0, TR 8.98.2.3
AS400 Enterprise Server - 6.1
WebSphere 6.1 running on Windows 2003