SSL setup?

[larshp]

see abapGit/abapGit#306

@nununo

[larshp]

@nununo do you get the invalid certificate error when accessing the .git URL via browser? What is the error message in abapGit?

what kind of login method is used when accessing the web part?

try checking some of the following settings:
https://scn.sap.com/thread/3166828
https://scn.sap.com/thread/3492784
https://scn.sap.com/thread/3379951

perhaps try adding ?sap-system-login-basic_auth=X to the .git clone URL

also try modifying the url in https://github.com/larshp/abapGit/wiki/ZABAPGIT_TEST_SSL to see if it works, it might be easier to debug

[nununo]

We're using single sign-on so I assumed it would be automatic.
I'm not very familiar with web services in SAP so here's a screenshot of the logon data:

After some I added the client/user/pass logon data and then removed somehow the url is now HTTP instead of HTTPS and the port is different. So I now have a normal HTTP url for the .git file.

When I try to access it through the browser it is automatically downloaded as a file with 318 bytes with binary content.

But when I try to clone the repository, after some debugging I found that the URL get's a temporary redirect into the Single Sign-On system, the original URL is replaced by the new SSO url and... that's it: HTTP Communication Failure.

I'm now trying to understand how I can configure the SICF service in order to bypass the SSO... but I still didn't figured it out.

I'll keep trying... and will try to get someone BASIS to help me.

At least now the problem is identified and it doesn't seem to be a problem with abapGitServer ;) Unless you think it should be able to cope with this SSO issue.

Cheers,
Nuno

[nununo]

Solved. Everything is working now. I configured it in a way that the SSO is no longer in the middle.
Thanks for all the help! This problem was unrelated to SSL after all. Sorry for the confusion.

[larshp]

was it a setting in SICF for ZGIT? can you add a few notes on how to fix it if somebody else experiences the same issue in the future?

[nununo]

Sure! What I did was:

• Set the procedure from "Standard" to "Require Logon Data"
• Fill in the Client, User and Password

And that was enough to make it work! I hope this helps others!

It hadn't tried it before because I was misled to think that the issue was related to SSL.

Question: why did you call the service ZGIT instead of ZABAPGITSERVER? It would have been more coherent with the project naming.

[larshp]

just to have a shorter URL, my guess is it wont conflict with anything else, we can change it if you like

[nununo]

I think name coherence is very important in any project. If someone finds this service called ZGIT it will not be obvious if it is related to abapGit or abapGitServer. It's ambiguous. I'd give it a more explicit name like ZABAPGITSERVER. If this is possible of course, otherwise... not a big deal ;)

[larshp]

good idea

[larshp]

fixed, SICF service renamed from ZGIT to ZABAPGITSERVER, note that ZGIT service has to be deleted manually after pulling