System is unable to interpret the SSO ticket received

Hi,
We are trying to establish SSO between portal and backend system.
We exported the Portal ticket to backend system and add to ACL list
still we are facing problem in establishing SSO between portal and backend system
Please help me in resolving this issue
point will be awarded for sure
Bala

Hi,
Please check this blog:
User Mapping-based Single Sign On
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6b1472a7-0301-0010-64bd-dc96509db6f7
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/ep/sso%2bchecklist
Quick Guide for setting up SSO between EP and R/3
Connecting SAP systems to Enterprise portal with SSO.
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/ep/single%2bsign-on%2band%2bcookies
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.highlightedcontent?documenturi=%2fhelp%2fsdn_help_nw04s%2fsaphelp_nw04s%2fhelpdata%2fen%2fd3%2f41c8ecb31d11d5993800508b6b8b11%2fcontent.htm
Hope this helps...
Regards,
Mona
Edited by: Mona Kapur on Jan 11, 2008 1:54 AM
Edited by: Mona Kapur on Jan 11, 2008 2:00 AM

Similar Messages

We got error "System is unable to interpret the SSO ticket received"

We got error "System is unable to interpret the SSO ticket received" on Backend system(R/3 4.7).
We use SAP Enterprise Portal 6.0 SP15.
Please let us know what is problems ?
We done following steps in SAP EP.
1. Created LOGON-METHOD (Logon Method : SAPLOGONTICKET).
2. Export Public-key (verify.der) from SAP EP.
   (System Admin -> System config -> Keystore Administration -> Download)
We done following steps in SAP R/3.
3. Start STRUSTSSO2 Transaction.
   In the PSE status frame on the left, choose the system PSE.
   In the certificate section, choose Import Certificate.
     The Import Certificate screen appears.
   Choose the File tab.
   In the File path field, enter the path of the portal's verify.der file.
   Set the file format to DER coded and confirm.
   In the Trust Manager, choose Add to PSE.
   Choose Add to ACL, to add the Portal Server to the ACL list.
   In the dialog box that appears, enter follows:
     system ID    :J2E
     client       :000
     Subject name :CN=J2E
     Issuer name :CN=J2E
     Serial number:00
   Save your entry.
4. Set profile parameters
   login/accept_sso2_ticket = 1
   login/create_sso2_ticket = 0
5. Restart SAP R/3 system.

Hi,
I faced the same problem when i am configuring the SSO,
check the portal client number in System Administration>System Configaration->UM Configuration--->Direct Editing
and give the same client number
In the dialog box that appears,
system ID :J2E
client :000
else check weather u r importing the certificate correctly.
First export the verify.der and and import that using the STRUSTSSO2
Thanks
Ajay

The system is unable to interpret the SSO ticket received

Hi,
We are facing the following error. Could anyone please help us understand/resolve the same
com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: The system is unable to interpret the SSO ticket received
     at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java(Compiled Code))
     at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java(Compiled Code))
     at com.sap.mw.jco.JCO$Client.connect(JCO.java(Compiled Code))
     at com.sap.mw.jco.JCO$Pool.initPool(JCO.java(Compiled Code))
     at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java(Compiled Code))
     at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java(Inlined Compiled Code))
     at com.sap.mw.jco.JCO.getClient(JCO.java(Inlined Compiled Code))
     at com.sap.mw.jco.webas.WebDynproExtension.addClientPool(WebDynproExtension.java(Compiled Code))
     at com.sap.mw.jco.webas.WebDynproExtension.addClientPool(WebDynproExtension.java(Compiled Code))
     at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.createPool(AbstractJCOClientConnection.java(Compiled Code))
     at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.checkPoolEntry(AbstractJCOClientConnection.java(Inlined Compiled Code))
     at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.getClient(AbstractJCOClientConnection.java(Compiled Code))
     at com.sap.pcuigp.xssfpm.wd.BackendConnections.connectModelInternal(BackendConnections.java:261)
     at com.sap.pcuigp.xssfpm.wd.BackendConnections.initBackend(BackendConnections.java:226)
     at com.sap.pcuigp.xssfpm.wd.BackendConnections.connectModel(BackendConnections.java:159)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalBackendConnections.connectModel(InternalBackendConnections.java:183)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.connectModel(FPMComponent.java:699)
     at com.sap.pcuigp.xssfpm.wd.BackendConnections.init(BackendConnections.java:138)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalBackendConnections.init(InternalBackendConnections.java:179)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:170)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java(Compiled Code))
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java(Inlined Compiled Code))
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java(Inlined Compiled Code))
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java(Compiled Code))
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:382)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:618)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
     at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java(Compiled Code))
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code))
     at java.security.AccessController.doPrivileged1(Native Method)
     at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))
- Harshal

Hello Erin,
1. Can you please confirm whether what type of SSO concept has been configured....whether Logon Tickets or user mapping?
If logon tickets, just check once if the same user-id exists on both systems.....
2. Can you also try pinging & testing the JCo in hte SLD....just confirmation.
Awaiting Reply.
Warm Regards,
Ritu

RFC_ERROR_LOGON_FAILURE: The system is unable to interpret the SSO ticket

Hi folks,
i've here an issue that i could not solve, i've implemented SSO between SAP EP and SAP ERP 2005 several times but this time i've the error message
" The system is unable to interpret the SSO ticket received"
I've already imported portal certificate, put parameters in instance profile and restart ERP but it still gave the error, i found the same issue from others sdn users but none of then have the solution for me.
Could anyone help me here?
This is a urgent matter.
thanks in advance,
Pedro Rodrigues

Hi Pedro,
what result do you get in a connection test in the portal ?
To do that :
open the System definition (under System Administrator/System Configuration);
Open the ERP 2005 system entry> "Connection Test"
Select "Connection test for Connector".
Also make sure that the domain of both systems (portal and ERP) are the same e.g. portal.company.com and erp.company.com . IP addresses are not working in SSO....
Also helpful is the OSS 701205 which has a attached PAR file for testing the SSO.
Regards,
Kai

Unable to interpret the prtdiag o/p for CPU Slots & Memory DIIMS - V890

Unable to interpret the prtdiag o/p for CPU slots & Memory DIIMS on V890 server. Went through the sun docs for V890, but lead to lot of confusion.
your help on this would be appreciative.
Thanks

Hi,
below is the sample prtdiag output I've taken from a lab machine
System Configuration: Sun Microsystems sun4u Sun Fire V890
System clock frequency: 150 MHz
Memory size: 65536 Megabytes
========================= CPUs ===============================================
Run E$ CPU CPU
Brd CPU MHz MB Impl. Mask
A 0, 16 1500 32.0 US-IV+ 2.2
B 1, 17 1500 32.0 US-IV+ 2.2
A 2, 18 1500 32.0 US-IV+ 2.2
B 3, 19 1500 32.0 US-IV+ 2.2
C 4, 20 1500 32.0 US-IV+ 2.2
D 5, 21 1500 32.0 US-IV+ 2.2
C 6, 22 1500 32.0 US-IV+ 2.2
D 7, 23 1500 32.0 US-IV+ 2.2
========================= Memory Configuration ===============================
Logical Logical Logical
MC Bank Bank Bank DIMM Interleave Interleaved
Brd ID num size Status Size Factor with
A 0 0 2048MB no_status 1024MB 8-way 0
A 0 1 2048MB no_status 1024MB 8-way 0
A 0 2 2048MB no_status 1024MB 8-way 0
A 0 3 2048MB no_status 1024MB 8-way 0
B 1 0 2048MB no_status 1024MB 8-way 1
B 1 1 2048MB no_status 1024MB 8-way 1
B 1 2 2048MB no_status 1024MB 8-way 1
B 1 3 2048MB no_status 1024MB 8-way 1
A 2 0 2048MB no_status 1024MB 8-way 0
A 2 1 2048MB no_status 1024MB 8-way 0
A 2 2 2048MB no_status 1024MB 8-way 0
A 2 3 2048MB no_status 1024MB 8-way 0
B 3 0 2048MB no_status 1024MB 8-way 1
B 3 1 2048MB no_status 1024MB 8-way 1
B 3 2 2048MB no_status 1024MB 8-way 1
B 3 3 2048MB no_status 1024MB 8-way 1
C 4 0 2048MB no_status 1024MB 8-way 2
C 4 1 2048MB no_status 1024MB 8-way 2
C 4 2 2048MB no_status 1024MB 8-way 2
C 4 3 2048MB no_status 1024MB 8-way 2
D 5 0 2048MB no_status 1024MB 8-way 3
D 5 1 2048MB no_status 1024MB 8-way 3
D 5 2 2048MB no_status 1024MB 8-way 3
D 5 3 2048MB no_status 1024MB 8-way 3
C 6 0 2048MB no_status 1024MB 8-way 2
C 6 1 2048MB no_status 1024MB 8-way 2
C 6 2 2048MB no_status 1024MB 8-way 2
C 6 3 2048MB no_status 1024MB 8-way 2
D 7 0 2048MB no_status 1024MB 8-way 3
D 7 1 2048MB no_status 1024MB 8-way 3
D 7 2 2048MB no_status 1024MB 8-way 3
D 7 3 2048MB no_status 1024MB 8-way 3
<snip>
Board A, B, C & D represents 4 slots of the V890. Each slot has two CPU and associated memory slots ( 8 nos. for each CPU ) for each CPU.
Since its Sparc IV+ cpu, it has two cores and thus will have two CPU id associated with each physical CPU.
Slot A ==> CPU 0 & 2
Slot B ==> CPU 1 & 3
Slot C ==> CPU 4 & 6
Slot D ==> CPU 5 & 7
For memory interleaving and bank configuration, please go through below document.
http://docs.sun.com/source/817-3956-12/hw_config.html
HTH..
Mehul

OBIEE Writeback error - The system is unable to read the Write Back Templat

Hi all,
I'm trying to set up the write back feature for one of the reports. All the set up up including XML file in the custommessage folder is done.Ensured the webmessage name tag value (pmet_update) is same as the one used in the report write back template value etc.
Also the server is restarted after the latest XML file(as shown below) is copied after all type of debugging with similar threads on this matter.
But when i click on the update button in the report (button is highlighted), i'm getting the error
"The system is unable to read the Write Back Template 'pmet_update'. Please contact your system administrator."
here is the xml.
<?xml version="1.0" encoding="utf-8"?>
<WebMessageTables xmlns:sawm="com.siebel.analytics.web/message/v1">
<WebMessageTable lang="en-us" system="WriteBack" table="Messages">
<WebMessage name="pmet_update">
<XML>
<writeBack connectionPool="PMTCOG">
<insert></insert>
<update> UPDATE XREF_PMET_URL SET URL= '@{c1}' WHERE API='@{c0}'</update>
</writeBack>
</XML>
</WebMessage>
</WebMessageTable>
</WebMessageTables>
Could you please help?

Hi,
I think that you have to spacify also an SQL statement for the update tag, for example:
<?xml version="1.0" encoding="utf-8"?>
<WebMessageTables xmlns:sawm="com.siebel.analytics.web/message/v1">
<WebMessageTable lang="en-us" system="WriteBack" table="Messages">
<WebMessage name="pmet_update">
<XML>
<writeBack connectionPool="PMTCOG">
<insert> select null from dual</insert>
<update> UPDATE XREF_PMET_URL SET URL= '@{c1}' WHERE API='@{c0}'</update>
</writeBack>
</XML>
</WebMessage>
</WebMessageTable>
</WebMessageTables>
The witeback wants for both the tags (<insert></insert> and <update></update>) an SQL Statement.
For me it works.
Let me know!
Gianluca Ancarani

Write Back Error The system is unable to read the Write Back Template 'test

Write Back Error The system is unable to read the Write Back Template 'test'. Please contact your system administrator. OK
But, the update button is on.
It did work and now it doesn't... nothing of course that we know of has changed. We got this message when we started and the name of the file was what we put as template name in obiee instead of webmessage name but the update button was off.... now we have update button on and same error.
File is on unix and we have made 777 so it's open to the world.
<?xml version="1.0" encoding="utf-8"?>
<WebMessageTables xmlns:sawm="com.siebel.analytics.web/message/v1">
<WebMessageTable lang="en-us" system="WriteBack" table="D_EXEC_METRIC">
<WebMessage name="test">
<XML>
<writeBack connectionPool="writeback">
<update>UPDATE D_EXEC_METRIC SET EXEC_METRIC_ICON_WID = @{c3}, EXEC_METRIC_COMMENT='@{c7}' WHERE SECTOR_WID=@{c0} AND EXEC_METRIC_WID=@{c2}</update>
</writeBack>
</XML>
</WebMessage>
</WebMessageTable>
</WebMessageTables>
thanks in advance for your help!

You're better off searching for an answer to this question in the [OBIEE Forum|http://forums.oracle.com/forums/forum.jspa?forumID=378].
The topic is discussed at least twice a month so there's tons of posts with all the answers you need. Make a forum search for writeback and you'll have your answer.
Cheers,
C.

10g - write back - The system is unable to read the Write Back Template

hi,experts,
I enabled write back on a report.
the button (write back) is enabled (not grey)
but when I click the button, there is a message
The system is unable to read the Write Back Template 'UPDATETESTWRITEBACK'. Please contact your system administrator.
I put UPDATETESTWRITEBACK.XML in C:\OracleBI\web\msgdb\customMessages
the syntax in the xml is correct.
what is the result? any log to check?

Its not mandatory to have the same template name as your xml file name.
But the <WebMessage name= "UPDATETESTWRITEBACK"> should be same what the templetae you are using in the webcat.
Please find sampel xml which can have any xyz name in the folder "OracleBIData\web\msgdb\customMessages'
<?xml version="1.0" encoding="utf-8" ?>
<WebMessageTables xmlns:sawm="com.siebel.analytics.web.messageSystem">
<WebMessageTable lang="en-us" system="WriteBackTemplates" table="Templates">
<WebMessage name= "ResourceAllocation">
<XML>
<writeBack connectionPool="--your connection pool name">
<insert> Insert statement </insert>
</writeBack>
</XML>
</WebMessage>
</WebMessageTable>
</WebMessageTables>
Cheers,
Rajeev A

Unable to find the Message Interface Receiver Determination

Hi Everyone,
I am unable to find the Message Interface Receiver Determination in the SAP BASIS 7.0 --> http://sap.com/xi/XI/System. in IR.
I am using P.I 7.0 SP 15
Could anyone let me know what could be the problem.
Regards,
Varun

Hi Sridhar,
I cant find the Message Interface Receiver Determination in IR under the standard SWCV SAP BASIS 7.0 and under the namespace http://sap.com/xi/XI/System. in IR.This Message Interface will be useful while configuring in enhanced Receiver Determination.
http://help.sap.com/saphelp_nw2004s/helpdata/EN/84/e8763c997fda50e10000000a11405a/frameset.htm
Regards,
Varun

Where to get the SSO ticket for a JCO-Connection from?

Hey All,
The szenario is, I've got a Java application and I want to connect to a SAP System. For this I want to use SSO. In the documentation of JCO I found this phrase:
For SSO specify the user to be $MYSAPSSO2$ and pass the base64 encoded ticket as as the passwd parameter.
Well... Now my question... Where to get this base64 ticket from? The problem is, I'm NOT using WebDynpro, it's a custom application running on client side. Now how to get the needed information? (PSE?)
It would be great when you could give me a clue.
Best regards,
Kristian

This linksactualy leads to the same place I mentioned where
it installs the
player over the Internet
Another thing is that these players are said to be different
for different
browsers which means they are working together with a
browser. I am looking
for a player which allows to play SWF file directly, without
a browser.
I have such a player installed together with FLASH-8 - I am
looking for
such a player
"DMennenoh" <[email protected]> wrote in
message
news:e2qgmu$t5r$[email protected]..
> Does this help:
>
http://www.macromedia.com/shockwave/download/alternates/
>
> --
> Dave -
> Adobe Community Expert
> www.blurredistinction.com
> www.macromedia.com/support/forums/team_macromedia/
>
>

Unable to Interpret SSO Ticket Recieved.

Hai ,
While working in ESS , I tried to create travel request. While creating i recieved Error message.
Error: System is Unable to Interpret SSO ticket recieved.
Kindly Help me out.
Regards
ArunRajan,
Hosur

Hi,
Please check tha SSO is configured correclty & test is fine from both Portal & Back-end side.
Please refer to
[http://help.sap.com/saphelp_nw70/helpdata/EN/4d/dd9b9ce80311d5995500508b6b8b11/content.htm|http://help.sap.com/saphelp_nw70/helpdata/EN/4d/dd9b9ce80311d5995500508b6b8b11/content.htm]
In case you still face an issue, then please let me know.

Unable to open the XML files in Nakisa

Hi Gurus,
We are unable to open certain XML files in Nakisa. They show up as encrypted in the notepad or fail to open using the XML Marker. The files in question are
AppResources.xml
LoginConfiguration_SAP_Standard
LoginConfiguration_Anonymous
Purpose: We want to enable the SSO with the portal . We have checked the radio button but nakisa does not recognize the SSO ticket from the portal (Any folder in Nakisa where we need to place the Portal ticket?)
Also we want Nakisa to show the org chart for the logged in user. Luke had mentioned that some changes need to be made in the AppResources.xml (hope i correctly remember this) and we were looking to make these changes (rather try out.. any pointers please..?)
Thanks and Regards,
Arun E V

Hi Arun,
These files are encrypted. If your organisation is a partner with Nakisa you can obtain the decrypter from them.
Portal SSO works without any configuration directly in the XML files. If you are getting an error stating that the Portal ticket cannot be interpreted then your configuration is not correct. In your URL iView you need to ensure the fully qualified domain name (FQDN) is used for the application URL. In the Administrator Console you need to ensure you enter the system details (Host, Sys Nr and Client) for the backend system which holds your SSO ticket for that Portal. You need to use FQDN here too.
There is additional security configuration that can be done in the XML files but SSO will still work with just the Administrator Console configuration.
I hope that helps!
Luke

A failure occured while importing Java SSO ticket certificate in ABAP stack Exception : FOREIGN_ENQUEUE_LOCK

Dear All,
We have completed the fresh installation of Soman7.1.
Now , We are doing the "Configuration of the Solman" and we are in the Step "Basic configuration ".
SID: SMI
Hostname: Solmantrg
Solman version: 7.1
The SSO Setup is failing with below error.
Message :
A failure occured while connecting to ABAP stack on solmantrg.thetimes.co.in sys=01 client=001 user=null. Details : 'user' missing
Details of the Log
Found SID for SSO ACL entry : SMI
Found login.ticket_client for SSO ACL entry : 000
The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tc~webadministrator~solmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (619 bytes)
ABAP SSO ticket certificate of SMI was imported in ABAP PSE of solmantrg.thetimes.co.in (client 001)
The ABAP SSO ticket certificate was successfully imported in ABAP System PSE, and the ACL updated accordingly (SID=SMI LoginTicketClient=001)
A failure occured while importing Java SSO ticket certificate in ABAP stack
!! Exception : FOREIGN_ENQUEUE_LOCK(Abap cause=SOLMAN_ADMINE_TABLEE)
The ABAP instance profile contains the parameter : login/accept_sso2_ticket=1
The SSO ticket Certificate <CN=SMI> has been successfully imported into Java Keystore
The com.sap.security.core.server.jaas.EvaluateTicketLoginModule already contained the entry : trustedsys=SMI, 001 trustediss=CN=SMI trusteddn=CN=SMI
The Authentication template for component sap.com/SQLTrace*OpenSQLMonitors was already set to ticket
The Authentication template for component sap.com/SQLTrace*SQLTrace was already set to ticket
The Authentication template for component sap.com/tc~monitoring~systeminfo*monitoring was already set to ticket
The Authentication template for component sap.com/tc~monitoring~systeminfo*sap_monitoring was already set to ticket
The Authentication template for component sap.com/com.sap.security.core.admin*useradmin was already set to ticket
The Authentication template for component sap.com/tc~webadministrator~solmandiag*smd was already set to ticket
The Authentication template for component sap.com/tc~smd~e2etraceupload*E2EClientTraceUploadW was already set to ticket
The com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule already contained the entry : trustedsys=SMI, 001 trustediss=CN=SMI trusteddn=CN=SMI
The Authentication template for component sap.com/tc~smd~EemAdminGateway*EemAdmin_Config1 has been set to evaluate_assertion_ticket
The Login Module BasicPasswordLoginModule was added to the security component sap.com/tc~smd~EemAdminGateway*EemAdmin_Config1
A failure occured while connecting to ABAP stack on solmantrg.thetimes.co.in sys=01 client=001 user=null
!! Exception : 'user' missing
The ABAP instance profile contains the parameter : login/create_sso2_ticket=2
Exception
com.sap.mw.jco.JCO$AbapException: (126) FOREIGN_ENQUEUE_LOCK: FOREIGN_ENQUEUE_LOCK
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1512)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3937)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3570)
at com.sap.sup.admin.setup.AbapSysRfcAdapter.addTrustedIssuer(AbapSysRfcAdapter.java:276)
at com.sap.sup.admin.setup.AbapSysRfcAdapter.addTrustedIssuer(AbapSysRfcAdapter.java:249)
at com.sap.sup.admin.setup.ManagingServices.setupDualStackSSO(ManagingServices.java:752)
at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:564)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:445)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:674)
at com.sap.sup.admin.setup.ws.SetupWrapper._diagSetup(SetupWrapper.java:279)
at com.sap.sup.admin.setup.ws.SetupWrapper.diagSetup(SetupWrapper.java:21)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.services.webservices.runtime.JavaClassImplementationContainer.invokeMethod(JavaClassImplementationContainer.java:76)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:174)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:81)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:90)
at SoapServlet.doPost(SoapServlet.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
========================
com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'user' missing
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:518)
at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1087)
at com.sap.mw.jco.JCO$Client.connect(JCO.java:3310)
at com.sap.sup.admin.setup.CommonServices.getJcoClient(CommonServices.java:773)
at com.sap.sup.admin.setup.CommonServices.getJcoClient(CommonServices.java:722)
at com.sap.sup.admin.setup.SolManRfcAdapter.getJ2eeSsoSettings(SolManRfcAdapter.java:649)
at com.sap.sup.admin.setup.ManagingServices.updateSSOfromURLrepository(ManagingServices.java:790)
at com.sap.sup.admin.setup.ManagingServices.setupDualStackSSO(ManagingServices.java:773)
at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:564)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:445)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:674)
at com.sap.sup.admin.setup.ws.SetupWrapper._diagSetup(SetupWrapper.java:279)
at com.sap.sup.admin.setup.ws.SetupWrapper.diagSetup(SetupWrapper.java:21)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.services.webservices.runtime.JavaClassImplementationContainer.invokeMethod(JavaClassImplementationContainer.java:76)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:174)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:81)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:90)
at SoapServlet.doPost(SoapServlet.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
In strustsso2, cerficate date is valid only.
kindly help us to fix this SSO_Setup issue
Thanks and Regards,
Gayathri.K

Hi ,
Thanks for the above reply.
I have executed the Step 2.3 AND 2.4 and i started the SSO Setup again. Still i am getting below error
Message
A failure occured while importing Java SSO ticket certificate in ABAP stack
Details Of the Log
Found SID for SSO ACL entry : SMI
Found login.ticket_client for SSO ACL entry : 000
The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tc~webadministrator~solmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (619 bytes)
ABAP SSO ticket certificate of SMI was imported in ABAP PSE of solmantrg (client 001)
The ABAP SSO ticket certificate was successfully imported in ABAP System PSE, and the ACL updated accordingly (SID=SMI LoginTicketClient=001)
A failure occured while importing Java SSO ticket certificate in ABAP stack
!! Exception : FOREIGN_ENQUEUE_LOCK(Abap cause=SOLMAN_ADMINE_TABLEE)
The ABAP instance profile contains the parameter : login/accept_sso2_ticket=1
The SSO ticket Certificate <CN=SMI> has been successfully imported into Java Keystore
The com.sap.security.core.server.jaas.EvaluateTicketLoginModule already contained the entry : trustedsys=SMI, 001 trustediss=CN=SMI trusteddn=CN=SMI
The Authentication template for component sap.com/SQLTrace*OpenSQLMonitors was already set to ticket
The Authentication template for component sap.com/SQLTrace*SQLTrace was already set to ticket
The Authentication template for component sap.com/tc~monitoring~systeminfo*monitoring was already set to ticket
The Authentication template for component sap.com/tc~monitoring~systeminfo*sap_monitoring was already set to ticket
The Authentication template for component sap.com/com.sap.security.core.admin*useradmin was already set to ticket
The Authentication template for component sap.com/tc~webadministrator~solmandiag*smd was already set to ticket
The Authentication template for component sap.com/tc~smd~e2etraceupload*E2EClientTraceUploadW was already set to ticket
The com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule already contained the entry : trustedsys=SMI, 001 trustediss=CN=SMI trusteddn=CN=SMI
The Authentication template for component sap.com/tc~smd~EemAdminGateway*EemAdmin_Config1 has been set to evaluate_assertion_ticket
The Login Module BasicPasswordLoginModule was added to the security component sap.com/tc~smd~EemAdminGateway*EemAdmin_Config1
The ABAP instance profile contains the parameter : login/create_sso2_ticket=2
Exception
com.sap.mw.jco.JCO$AbapException: (126) FOREIGN_ENQUEUE_LOCK: FOREIGN_ENQUEUE_LOCK
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1512)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3937)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3570)
at com.sap.sup.admin.setup.AbapSysRfcAdapter.addTrustedIssuer(AbapSysRfcAdapter.java:276)
at com.sap.sup.admin.setup.AbapSysRfcAdapter.addTrustedIssuer(AbapSysRfcAdapter.java:249)
at com.sap.sup.admin.setup.ManagingServices.setupDualStackSSO(ManagingServices.java:752)
at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:564)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:445)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:674)
at com.sap.sup.admin.setup.ws.SetupWrapper._diagSetup(SetupWrapper.java:279)
at com.sap.sup.admin.setup.ws.SetupWrapper.diagSetup(SetupWrapper.java:21)
at sun.reflect.GeneratedMethodAccessor2202.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.services.webservices.runtime.JavaClassImplementationContainer.invokeMethod(JavaClassImplementationContainer.java:76)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:174)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:81)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:90)
at SoapServlet.doPost(SoapServlet.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Also , i have checked the note # 1008474 Diagnostics Setup Wizard uses wrong ABAP client.
As mentioned in above note, i have checked in visual admin all settings are maintained correctly.
RFC destination WEBADMIN & SOLMANDIAG is also working fine.
please tel why i am getting Foreign Enquelock
Regards,
Gayathri.K

Multiple SSO Tickets Cause Problem

Dear SAP Fellas,
Our customer implemented NWBC based travel management into ECC6 based HR system.
It uses its own SSO tickets, when users log on via webbrowser, it is working fine.
In this landscape there is an Enterprise Portal used for other purposes, but also issues its own SSO tickets.
When this portal is also used at the same time or was used before (so an 'alien' SSO ticket is in the browser's cache), ECC6 changes logon style, username and password fields are greyed out and asks user to press a button for an additional popup window, where username and password can be typed in. This behavior breaks NWBC's operation internally, every clicks on menuitems invokes this password window.
Do you know any way to teach this ECC6 system to process only its own SSO ticket and ignore others?
Thank you for answers in advance.

Dear SAP Fellas,
Our customer implemented NWBC based travel management into ECC6 based HR system.
It uses its own SSO tickets, when users log on via webbrowser, it is working fine.
In this landscape there is an Enterprise Portal used for other purposes, but also issues its own SSO tickets.
When this portal is also used at the same time or was used before (so an 'alien' SSO ticket is in the browser's cache), ECC6 changes logon style, username and password fields are greyed out and asks user to press a button for an additional popup window, where username and password can be typed in. This behavior breaks NWBC's operation internally, every clicks on menuitems invokes this password window.
Do you know any way to teach this ECC6 system to process only its own SSO ticket and ignore others?
Thank you for answers in advance.

Setting of SSO ticket life time in EP7

Hi guys,
We are having some problem with the lifetime of the SSO ticket, it will auto expire in less than 5 minutes time.
These are what we have done so far:
1) In RZ10, set the "login/accept_sso2_ticket = 1", "login/create_sso2_ticket = 1", "login/ticket_expiration_time = 48"
2) set the ITS timeout as 3600 seconds
3) set the UME property login.ticket_lifetime to 8 hours (Default)
FYI, we are using EP7.0 with the 4.6C.
I remember that in EP6, we can set it under the System Administration > System Configuration > UM Configurations > Security Settings > Lifetime of SAP Logon Ticket
However, in EP7 we can't find any setting for logon ticket under the System Administration > System Configuration > UME Configurations > Security Policy
Do you have any similar experience in your previous project before?
Appreciate for any suggestion or comment.
Thanks,
Justin Yee

Hi Justin,
You can also use the Global settings in Visual Admin. UME Provider service has property SSO_Ticket_Lifetime.
Best regards,
Jan Laros

System is unable to interpret the SSO ticket received

Similar Messages

Maybe you are looking for