Re: MYSAPSSO2: ABAP backend shows empty SYSID and CLIENT
It seems to be a kernel version problem. Kernel 720 patch level 401 gives the errors above, kernel 721 patch level 311 works fine: N Tue Jul 1 11:31:22 2014N dy_signi_ext: LOGON TICKET logon (client...
View ArticleRe: NW SSO x.509 based configuration
Hello, you have changed the enrollURL to the fully qualified hostname vairant in the Secure Login Server administrator console, but there was maybe no update of the policy on the client.Try to change...
View ArticleClik here to view.
Re: NW SSO x.509 based configuration
Dear Alexander, I manually edited the entry as suggested by you, but still the sam error.
View ArticleRe: NW SSO x.509 based configuration
Dear Sam, Could you please provide the Secure Login Client traces after you change the enrollurl0.The output of the command "klist" on your client workstation could help too.KR Valerie
View ArticleRe: NW SSO x.509 based configuration
Hello, then we have an problem with the SPN/Kerberos configuration.Could you check on the Active Directory Server with the command "setspn -Q HTTP/srvpid01.LDAP-TEST.dom" and check fi there are double...
View ArticleRe: MYSAPSSO2: ABAP backend shows empty SYSID and CLIENT
That's interesting. I wonder what fixed this. I assume it's SAP note 1831580.
View ArticleRe: NW SSO x.509 based configuration
Dear Valerie, Please find below the trace..----------------------------------------------------------------------------[YYYY.MM.DD HH:MM:SS.MIKROS][LEVEL][PROCESS ][MODULE ][THR_ID]...
View ArticleRe: NW SSO x.509 based configuration
Dear Alexander, Please find below the outputsetspn -Q HTTP/srvpid01.LDAP-TEST.domChecking domain DC=LDAP-TEST,DC=domCN=SAP SSO BID,CN=Users,DC=LDAP-TEST,DC=dom HTTPS/srvpid01.LDAP-TEST.dom...
View ArticleRe: MYSAPSSO2: ABAP backend shows empty SYSID and CLIENT
That is indeed very plausible as it impacts one of the ACL line fields, but I still don't see why the sysID or the client came through empty... Pity the trace doesn't display which serial it finds in...
View ArticleClik here to view.
Re: NW SSO x.509 based configuration
Dear Valerie, i have teh value p:CN=SAP-SSO-SRD@LDAP-TEST.dom for the parameter snc/identity/as [ this was done when i did the spnego configuration] Please see below the the content of psePlease...
View ArticleRe: NW SSO x.509 based configuration
Dear Saam, This look like your SSL server certifcate. Did you create a SAP server certificate using the Secure Login Administration Console with the DName CN=SAP-SSO-SRD@LDAP-TEST.dom ? And you try to...
View ArticleClik here to view.
Re: NW SSO x.509 based configuration
Dear Valerie, I created a new certificate and managed to import it using strust. Now when i try to connect i getRegards,Sam
View ArticleRe: NW SSO x.509 based configuration
Dear Valerie,I managed to fix the above error. Now when i login , i get the logon screen and below the error "NO user exists with the SNC name "p:CN=CSAM" Regards,Sam
View ArticleRe: NW SSO x.509 based configuration
Dear Sam, Did you configure the SNC Name of users using trnsaction su01 or snc1?The error you get means, that your configuration of Secure Login Library, Secure Login Client and Secure Login Server is...
View ArticleRe: NW SSO x.509 based configuration
Dear Valerie, Yes, correctly pointed out.Did the required changes in SU01 and it worked. Really appreciate the kind of support you and Mr.Alexander provided in fixing the issues which we have faced....
View ArticleRe: NW SSO x.509 based configuration
Dear Sam,Happy to read, that your configuration is OK now. The OSS support would have help you too. I suppose that you are asking if it is possible to use SPNego and SNC for ABAP togehter right?Both...
View ArticleRe: Secure Login Client - Started without access to network
Hello, I have made some experiments with SSL port configuration and you are right, the Secure Login Client 2.0 SP2 and SP3 has the same behavior with SSL client authentication modes. So this cannot...
View ArticleRe: SAML 2.0 backwards compatible?
Dear Setu, As a protocol, SAML has three versions: SAML 1.0, SAML 1.1, and SAML 2.0. SAML 2.0 is an enhancement to the previous SAML 1.x specifications, but is not backwards compatible. Best regards,...
View ArticleRe: Secure Login Client - Started without access to network
Hello Alexander, I am attaching the full traces for SP2 and SP3. Hope this helps. The profile that is being used should not be important, as current settings works with SP2 and not with SP3, or do I...
View ArticleRe: SSO between SUS and SRM
Hi all, I am a colleague of David and I am continuing the implementation of the SSO between SRM and SUS. Just to resume, as David says we are willing to configure the access to SRM BSP through HTTPS...
View Article