Skip to Content
avatar image
Former Member

SM59 Authorization test (SNC required for this connection)

Hello,

I have just recently setup SSO in our test systems and received some intermittent error when checking the authorization test of RFC ABAP Connection. We have specific job that's connecting to our EWM test to ERP test system via RFC ABAP Connection. The job sometimes successfully finished and sometimes not. It is giving error "SNC required for this connection" and when I checked the target system in SM59 and check the authorization test it is giving the same error. But after some minutes the authorization test went successfully and the job was successfully finished also.

For SSO this are the parameters I set:

Any idea on this error?

Additionally, I checked sm21 and st22 but I didn't find anything related to the error. Also in our development systems where SSO is also setup, we didn't received the same issue.

Regards,

Florence

parameters.JPG (52.0 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Nov 14, 2014 at 11:40 AM

    Hi Florence,

    If your SNC is active and if the parameter snc/accept_insecure_gui is set to 1 then everything should work fine.

    But as in your case, you said it works sometimes and sometimes it doesn't work which is little weird. So can you please confirm if you had set this parameter in the DEFAULT.PFL?

    As a workaround you can check the option "Password Logon for SAP GUI permitted" under SNC tab in SU01 for the RFC user and then check.

    Regards,

    Nirmal.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi.

      Yes the issue is sporadic. Right now it just finished 4 successfully run. But this is really kind of weird. other RFC Abap connections are working fine when testing the authorization. This is just for one RFC abap connection.

      Looks like I already found the answer. In our EWM test I missed out this parameter (snc/accept_insecure/rfc =1). I will try and check.

      Anyways, Thank you Nirmal for the help! 😊

      Regards,

      Florence

  • Nov 14, 2014 at 12:48 PM

    Such sporadic SNC issues are known from message server environments, where one or more instances have a missing or bogus SNC configuration, like a bad password was entered as Kerberos credentials.

    Do you test with single instances, or is message server involved?

    -- Stephan

    Add comment
    10|10000 characters needed characters exceeded

    • That´s right, Florence. My hint was just about checking all instance configurations if they are really the same. A wrong or missing SNC server configuration can cause different client errors.

      -- Stephan