on 07-02-2008 12:19 PM
Hi,
We have done a system copy of our PRD system to a new QAS server with new server host name. We also have a new ITS server with a new host name as well. So we now have 2 QAS R/3 systems and 1 portal QAS. I have reconfigured the portal system landscape to point to the new QAS R/3 system but since then SSO has not worked. Here is what I have done :
1) Through RZ10 added the following parameters to the instance profile :
login/accept_sso2_ticket=1
login/create_sso2_ticket
Checked in SSO2 and login tickets accepted.
2) Added FQDN to instance profile parameter icm/host_name_full in RZ10
3) in STRUSTSSO2 deleted old System PSE and created new.
4) Exported tickets from Portal and added to STRUSTSSO2. Added to certifcate and ACL. Ticket has not expired
5) Recreated sso tickets and imported back into R/3 with STRUSTSSO2 but still no luck.
Can anyone help ? Do I need to make any changes in Visual Administrator ? Like adding new r/3 hostname ??
Thanks
Craig
check these links
https://forums.sdn.sap.com/click.jspa?searchID=13478788&messageID=5478166
https://forums.sdn.sap.com/click.jspa?searchID=13478788&messageID=5429973
https://forums.sdn.sap.com/click.jspa?searchID=13478788&messageID=5321462
https://forums.sdn.sap.com/click.jspa?searchID=13478788&messageID=5141524
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Check the connections between the system.
Navigate to system and right click open connections and test the connection.
You can check in other way also go to se80 and then open bsp and open ss0 something .bsp and test the preview.
Thanks and Regards,
gopal.sattiraju
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
allrite ..lets get to this issue...
check the following :
1. check T-code SSO2 and determine the correct information about the logon tickets
2. make sure u have authentication type as SAPLOGONTICKET or user mapping depending on ur case.
3. define the alias with SIDCLNT<client no>
check t-code BD54 for the right logical system name
and t-code SMICM (shift +f1) for the right FQDN and the port no
.....here is another tool for you..Note 1083421
run the tool and lets see what happens..
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.