SMP HTTP Registration Error

[nageshcaparthy]

Dear All,

I am trying to do a Basic Authentication with UN and Pass on SMP3 SP10 PL05. Here are the following details:

1. I am able to ping the backend system

2. I am able to register from browser with no auth to SMP System

3. When I try with GW Sampleflight, i get 401 unauthorized(Login details are correct)

4. I did a gw trace and i am able to see the request and response

5. SMP server logs indicates "Authentication scheme negotiate not supported". Yes all the basic test are done, port are open between GW and SMP and they are communicating.

Here is the error log:

2016 03 08 09:14:16#+0300#DEBUG#com.sap.mobile.platform.server.online.filter.application.AbstractClientFilter###http-bio-8090-exec-10####xxxx-xxxx-xxxx-xxxx-xxxx#####>> POST /odata/applications/latest/com.test/Connections HTTP/1.1 |

2016 03 08 09:14:16#+0300#DEBUG#com.sap.mobile.platform.server.online.filter.application.AbstractClientFilter###http-bio-8090-exec-10####xxxx-xxxx-xxxx-xxxx-xxxx#####>> host: host.com:8090 |

2016 03 08 09:14:16#+0300#DEBUG#com.sap.mobile.platform.server.online.filter.application.AbstractClientFilter###http-bio-8090-exec-10####xxxx-xxxx-xxxx-xxxx-xxxx#####>> user-agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:44.0) Gecko/20100101 Firefox/44.0 |

2016 03 08 09:14:16#+0300#DEBUG#com.sap.mobile.platform.server.online.filter.application.AbstractClientFilter###http-bio-8090-exec-10####xxxx-xxxx-xxxx-xxxx-xxxx#####>> accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 |

2016 03 08 09:14:16#+0300#DEBUG#com.sap.mobile.platform.server.online.filter.application.AbstractClientFilter###http-bio-8090-exec-10####xxxx-xxxx-xxxx-xxxx-xxxx#####>> accept-language: null |

2016 03 08 09:14:16#+0300#DEBUG#com.sap.mobile.platform.server.online.filter.application.AbstractClientFilter###http-bio-8090-exec-10####xxxx-xxxx-xxxx-xxxx-xxxx#####>> accept-encoding: gzip, deflate |

2016 03 08 09:14:16#+0300#DEBUG#com.sap.mobile.platform.server.online.filter.application.AbstractClientFilter###http-bio-8090-exec-10####xxxx-xxxx-xxxx-xxxx-xxxx#####>> content-type: application/xml |

2016 03 08 09:14:16#+0300#DEBUG#com.sap.mobile.platform.server.online.filter.application.AbstractClientFilter###http-bio-8090-exec-10####xxxx-xxxx-xxxx-xxxx-xxxx#####>> content-length: 339 |

2016 03 08 09:14:16#+0300#DEBUG#com.sap.mobile.platform.server.online.filter.application.AbstractClientFilter###http-bio-8090-exec-10####xxxx-xxxx-xxxx-xxxx-xxxx#####>> connection: keep-alive |

2016 03 08 09:14:16#+0300#DEBUG#com.sap.mobile.platform.server.online.filter.application.AbstractClientFilter###http-bio-8090-exec-10####xxxx-xxxx-xxxx-xxxx-xxxx#####>> authorization: Basic xxxx== |

2016 03 08 09:14:16#+0300#WARN#com.sybase.security.http.HttpAuthenticationLoginModule$CustomCookieEchoTargetAuthenticationStrategy###http-bio-8090-exec-10##xxxx-8add-xxxx-xxxx-xxxx#com.test#xxxx-xxxx-xxxx-xxxx-xxxx#Registration####Authentication scheme negotiate not supported |

2016 03 08 09:14:16#+0300#WARN#com.sybase.security.http.HttpAuthenticationLoginModule###http-bio-8090-exec-10##xxxx-8add-xxxx-xxxx-xxxx#com.test#xxxx-xxxx-xxxx-xxxx-xxxx#Registration####Server responded with the status code "401" |

2016 03 08 09:14:16#+0300#ERROR#com.sap.mobile.platform.server.online.filter.application.AbstractSMPApplicationSettingsHandler###http-bio-8090-exec-10##xxxx-8add-xxxx-xxxx-xxxx#com.test#xxxx-xxxx-xxxx-xxxx-xxxx#Registration#401###401:Unauthorized |

2016 03 08 09:14:16#+0300#DEBUG#com.sap.mobile.platform.server.online.filter.application.AbstractClientFilter###http-bio-8090-exec-10##xxxx-8add-xxxx-xxxx-xxxx#com.test#xxxx-xxxx-xxxx-xxxx-xxxx#Registration#401###<< Status Code: 401 |

2016 03 08 09:14:16#+0300#DEBUG#com.sap.mobile.platform.server.online.filter.application.AbstractClientFilter###http-bio-8090-exec-10##xxxx-8add-xxxx-xxxx-xxxx#com.test#xxxx-xxxx-xxxx-xxxx-xxxx#Registration#401###<< WWW-Authenticate: Basic realm="Testing" |

Any suggestions pls.

Regards,

Nagesh

[Jitendra_Kansal · Accepted solution]

UN ?

Can you share backend, security profile settings for this app id?

Regards,

JK

[nageshcaparthy · Accepted solution]

Hi JK,

I have tried with SSO Mechanism as Basic and SSO2 and the security profile is HTTP/HTTPs with the Backend ping URL with GW http://xxxxx:8000/sap/bc/ping which has standard authentication and it works fine with the login details which I am using on REST Client.

Sample Flight oData: http://xxxx:8000/sap/opu/odata/iwfnd/rmtsampleflight/ which is also working fine with the login details.

Regards,

Nagesh

[nageshcaparthy · Accepted solution]

UN is username and password. sorry about the short form language.

[Jitendra_Kansal · Accepted solution]

You can use SSO2 mechanism only if OData producer supports MYSAPSSO2 token. Seems, for your case, it should work as its GW system.

I tried with publicly available service, registration is successful  https://sapes4.sapdevcenter.com/sap/opu/odata/IWFND/RMTSAMPLEFLIGHT/

I provided the same (above) url for BACKEND and also for url in security profile HTTP/HTTPS (also added MYSAPSSO2 as cookie name).

Can you try providing same urls in both places? Also, please share screenshot in case error persists.

Regards,

JK

[nageshcaparthy · Accepted solution]

Hi ,

Yes, I have tested with providing same URLs in both places and keeping Basic as the SSO mechanism. Here is the screens for the same:

Error screen from REST Client:

There is no response on Body.

Error Log from SMP:

#2.0#2016-03-09 02:34:31 PM#WARNING#Registration###Security#1457523271053012#xxxxx-a401-4777-9ed7-xxxxx#com.test#com.sybase.security.http.HttpAuthenticationLoginModule:login########997#####Server responded with the status code "401"#

#2.0#2016-03-09 02:34:31 PM#ERROR#Registration#401##Other#1457523271053013#xxxxx-a401-4777-9ed7-xxxxx#com.test#com.sap.mobile.platform.server.online.filter.application.AbstractSMPApplicationSettingsHandler:doInternalFilter########997#####401:Unauthorized#

#2.0#2016-03-09 02:34:31 PM#DEBUG#Registration#401##Client Request Trace#1457523271053014#xxxxx-a401-4777-9ed7-xxxxx#com.test#com.sap.mobile.platform.server.online.filter.application.AbstractClientFilter:doFilter########997#####<< Status Code: 401#

#2.0#2016-03-09 02:34:31 PM#DEBUG#Registration#401##Client Request Trace#1457523271053015#xxxxx-a401-4777-9ed7-xxxxx#com.test#com.sap.mobile.platform.server.online.filter.application.AbstractClientFilter:doFilter########997#####<< WWW-Authenticate: Basic realm="Testing"#

#2.0#2016-03-09 02:34:31 PM#FATAL#Client Request Trace####1457523271053000#xxxxx-a401-4777-9ed7-xxxxx#com.test#AbstractClientFilter:doFilter########997#####Unauthorized : {"responseCode":"401"}#

#2.0#2016-03-09 02:34:31 PM#WARNING#Registration###Other#1457523271053011#xxxxx-a401-4777-9ed7-xxxxx#com.test#org.apache.http.impl.client.AuthenticationStrategyImpl:select########997#####Authentication scheme negotiate not supported#

#2.0#2016-03-09 02:34:31 PM#DEBUG####Client Request Trace#1457523271053002#xxxxx-a401-4777-9ed7-xxxxx##com.sap.mobile.platform.server.online.filter.application.AbstractClientFilter:doFilter########997#####>> user-agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:44.0) Gecko/20100101 Firefox/44.0#

#2.0#2016-03-09 02:34:31 PM#DEBUG####Client Request Trace#1457523271053003#xxxxx-a401-4777-9ed7-xxxxx##com.sap.mobile.platform.server.online.filter.application.AbstractClientFilter:doFilter########997#####>> accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8#

#2.0#2016-03-09 02:34:31 PM#DEBUG####Client Request Trace#1457523271053004#xxxxx-a401-4777-9ed7-xxxxx##com.sap.mobile.platform.server.online.filter.application.AbstractClientFilter:doFilter########997#####>> accept-language: null#

#2.0#2016-03-09 02:34:31 PM#DEBUG####Client Request Trace#1457523271053005#xxxxx-a401-4777-9ed7-xxxxx##com.sap.mobile.platform.server.online.filter.application.AbstractClientFilter:doFilter########997#####>> accept-encoding: gzip, deflate#

#2.0#2016-03-09 02:34:31 PM#DEBUG####Client Request Trace#1457523271053006#xxxxx-a401-4777-9ed7-xxxxx##com.sap.mobile.platform.server.online.filter.application.AbstractClientFilter:doFilter########997#####>> authorization: Basic xxxxx==#

#2.0#2016-03-09 02:34:31 PM#DEBUG####Client Request Trace#1457523271053007#xxxxx-a401-4777-9ed7-xxxxx##com.sap.mobile.platform.server.online.filter.application.AbstractClientFilter:doFilter########997#####>> content-type: application/xml#

#2.0#2016-03-09 02:34:31 PM#DEBUG####Client Request Trace#1457523271053008#xxxxx-a401-4777-9ed7-xxxxx##com.sap.mobile.platform.server.online.filter.application.AbstractClientFilter:doFilter########997#####>> content-length: 368#

#2.0#2016-03-09 02:34:31 PM#DEBUG####Client Request Trace#1457523271053009#xxxxx-a401-4777-9ed7-xxxxx##com.sap.mobile.platform.server.online.filter.application.AbstractClientFilter:doFilter########997#####>> cookie: X-SMP-APPCID=92fbd857-02b7-4402-99ae-553106e0da5d; X-SUP-APPCID=92fbd857-02b7-4402-99ae-553106e0da5d; SMP_COOKIE_STORE_92fbd857-02b7-4402-99ae-553106e0da5d_0=H4sIAAAAAAAAALVSXW_aMBT9L0h9a7vw2VFpD9cfCS441PkAsmmqQhKckEAoCRiY9t_ntFvVPu1hmmT5Wveee3x8fb79aG3DTdK6b_HAhUfXnXZa161jWByaHKzFiROOAKUMCAMu4QwEwFZwAQzAAOTvqPfg1NQ46B2hEZgR-Oqt_hKRBmkOBYSC_RJ5g-81fVPRcAeABFCAhjAAKHSbAOwIctVZwUwqKU0fyfw5zTNrqAyE1FjqnMkZQ0IwBB6dcMgt5FZTUCzUbAqr4GFcfmXpMbJBRIgHDDGCMTgKg6AqIijnolJYBGQmhEXVA3U8GnFUWtD2KU655xumYKZzjhe2wah9XM7b7eWmMBKPehzRV9yJj19xcRFkCPkX6nPE_tQmrgeKr6HHL1Gfe9GJEBgjac8QcA-MeOErxnAGM4z9Ede6tB5zrHoE0tLUyJgjaWH32XLZsksEfYALnXycBVUjeP_W3OTi84J4tKN_UU0J9Pk6MPisVOzDTHLKnYCaZj3L5h1vV-TZbCil0ddDX-BVSTLZNV6meta3815PK6acwAFSHzZXnbbGxelheTeq4nTdjUQfHzBanIK7HsOmIOguHjud-XBVdWE7yLPBxAyiaPW86sFVN9ZLW26X7KusqpNt3bpfhUWVXLfichNmW23D2yrchLeyPOpDAw3rVGc_6WOVRId98tZxbEhK3WL8vH4ztrb1k0tdl01tRp6sufvUNox3JhdyzQcD1RGWFTg5Svbl-bIbpmNsdQtyGhXSBvDNMPHn_t-l7m6qcHcjVRTe1O1_090QHapkH5XbOjnV7xQ3lajItIAvr0_5r4q-_wL7pDq9JAQAAA#

#2.0#2016-03-09 02:34:31 PM#DEBUG####Client Request Trace#1457523271053010#xxxxx-a401-4777-9ed7-xxxxx##com.sap.mobile.platform.server.online.filter.application.AbstractClientFilter:doFilter########997#####>> host: xxxxx:8090#

#2.0#2016-03-09 02:34:31 PM#DEBUG####Client Request Trace#1457523271053001#xxxxx-a401-4777-9ed7-xxxxx##com.sap.mobile.platform.server.online.filter.application.AbstractClientFilter:doFilter########997#####>> POST /odata/applications/latest/com.test/Connections HTTP/1.1#

Regards,

Nagesh

[Jitendra_Kansal · Accepted solution]

Hello Nagesh,

It should have worked. Under Authorization you have to pass backend credentials.

cc: Kevin Bates

You may check with SAP also via OSS ticket.

Regards,

JK

[nageshcaparthy · Accepted solution]

Thanks JK.

I see some issue with SPNEGO as its not supported and trying other alternatives. We have removed SPNEGO and trying with Basic test with external alias on GW. I still get same issue. Need  more time and working it.

Regards,

Nagesh

[nageshcaparthy · Accepted solution]

Hi JK / All,

I was able to solve this issue with the following changes in the HTTP/HTTPs authentication. Also I had to remove the Tick from Check Impersonation as the Token validation was not happening.

Hope it helps others too.

Regards,

Nagesh

[Jitendra_Kansal · Accepted solution]

Can you share more info on the values set for 'client HTTP values to Send' and 'Send Client HTTP Value as' ? Did you refer any document on this? would be interested to read more

Regards,

JK