docs: start user exits and authorizations

docs/ref-authorizations.md

@@ -0,0 +1,7 @@
+---
+title: Authorizations
+category: reference
+order: 50
+---
+
+todo, see https://github.com/larshp/abapGit/blob/52758028a7b08101e9c76d1cdab8639d776d3d2b/src/zabapgit.prog.abap#L35

docs/ref-exits.md

@@ -0,0 +1,42 @@
+---
+title: User Exits
+category: reference
+order: 40
+---
+
+abapGit contains predefined user exits which can be used to modify the standard behavior.
+
+
+If the compiled report is installed, create include `ZABAPGIT_USER_EXIT` and add local class `ZCL_ABAPGIT_USER_EXIT` implementing `ZIF_ABAPGIT_EXIT`.
+
+If the development version is installed create global class `ZCL_ABAPGIT_USER_EXIT` implementing `ZIF_ABAPGIT_EXIT`.
+
+In both cases add the object in a package different from the main abapGit code.
+
+The list of user exits can change at any time, make sure to syntax check user exits after upgrade of abapGit.
+
+### CHANGE_LOCAL_HOST
+If the hostnames are not properly configured, this exit can be used to modify the settings.
+This is especially useful when running abapGitServer on the local system.
+
+### ALLOW_SAP_OBJECTS
+Force allowing serialization of SAP objects.
+
+### CHANGE_PROXY_URL
+todo
+
+### CHANGE_PROXY_PORT
+todo
+
+### CHANGE_PROXY_AUTHENTICATION
+todo
+
+### CREATE_HTTP_CLIENT
+Store username and password in RFC connection setup, see [https://github.com/larshp/abapGit/issues/1841](https://github.com/larshp/abapGit/issues/1841)
+
+### HTTP_CLIENT
+Can be used for setting logon tickets eg. in connection with abapGitServer connections between SAP systems.
+[https://gist.github.com/larshp/71609852a79aa1e877f8c4020d18feac](https://gist.github.com/larshp/71609852a79aa1e877f8c4020d18feac)
+
+### CHANGE_TADIR
+Can be used to skip certian objects, or force a different object setup than currently in TADIR.