APAR status
Closed as program error.
Error description
Problem: We're trying to install TAM E-SSO 8.0.1.10, but we've run into some severe errors. The error shows when a user tries to log on the the engina through AccessAgent. Until then we've had no problems with AccessAdmin and IMS Configuration We can successfully ping and telnet (80 and 443) from the AA client machine to the IMS server. user cannot do initial sign up or login so there wallet is never stored on the machine. login using windows Gina bypass TAM E-SSO Gina ERROR: you do not have a wallet stored on the computer. However you cannot download your wallet from the IMS server beacuse network connectivity is currently unavailable. please try again later. this a new install not an upgrade This is exactly what steps we take: A. Setup IMS A.1 Install DB2 ESE 9.5 in accordance with the deployment redbook on TAM ESSO (Draft) A.2 Install IMS using the DB2 as datastore A.3 Configure IMS to connect to AD using a test-user called TAMESSO. A.4 Configured IMS using the AccessAdmin A.5 Installed AccessAgent on client desktop. A.6 Attempted signup/login from AA to IMS but both failed Advise if this user is created in Active Directory? Yes Advise if Active Directory snyc is enabled do you have user sync with Active directory? Yes Advice if the user has gone through first time login and created there secret questions? No, it fails before. Advice if when the user logged in for the first time that you selected YES to store the wallets locally on the machine? Wallets should be cached locally. We've never gotten to this question. Does this effect all users? Yes Can administrator login ok? No Ensure you have set the wallets to be stored locally We've set this up in IMS is the Access Agent greyed out when logging in? Yes - because we have to log directory on to Windows. You need to enable NetworkProvider - set it to Yes. Steps to Duplicate: See Problem Description Desired Behavior: Customer needs users to be able to login Environment: IMS: 8.0.1.0.10 AA: 8.0.1.0.11 OS the IMS Server is running on - Windows Server 2003 SP2 Which OS is the agent runnining on - Windows XP SP3 Which OS does the repository resides on - Windows Server 2003 SP2 Standard. Repository - AD Which type of configuration is the AccessAgent running under - Personal Desktop
Local fix
N/A
Problem summary
Ifix provided to customer
Problem conclusion
This will be shipped in ESSO 8.0.1 Fixpack 1
Temporary fix
Comments
APAR Information
APAR number
IZ52190
Reported component name
SSO ACCESS AGEN
Reported component ID
5724V67AG
Reported release
801
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-05-28
Closed date
2010-01-15
Last modified date
2010-01-15
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
SSO ACCESS AGEN
Fixed component ID
5724V67AG
Applicable component levels
R801 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSZU8Q","label":"IBM Security Access Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"801","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]
Document Information
Modified date:
23 September 2020