mirror of
https://github.com/abapGit/abapGit.git
synced 2025-05-01 04:08:27 +08:00
update links (#3979)
* update links * update links * Update package.json * Update guide-authentication.md
This commit is contained in:
parent
42c909e688
commit
bdfa168ba2
|
@ -1,6 +1,6 @@
|
|||

|
||||

|
||||
[](https://abapgit-slackinviter.herokuapp.com/)
|
||||
[](https://github.com/larshp/abapGit/blob/master/src/zif_abapgit_version.intf.abap)
|
||||
[](https://github.com/abapGit/abapGit/blob/master/src/zif_abapgit_version.intf.abap)
|
||||
|
||||
# abapGit
|
||||
|
||||
|
@ -40,7 +40,7 @@ You can find the contribution guidelines [here](CONTRIBUTING.md).
|
|||
See [dotabap.org](https://dotabap.org) or [this page](https://docs.abapgit.org/other-where-used.html).
|
||||
|
||||
## FAQ
|
||||
For questions/comments/bugs/feature requests/wishes please create an [issue](https://github.com/larshp/abapGit/issues)
|
||||
For questions/comments/bugs/feature requests/wishes please create an [issue](https://github.com/abapGit/abapGit/issues)
|
||||
|
||||

|
||||
|
||||
|
|
|
@ -3,7 +3,7 @@ title: Contributing
|
|||
order: 5
|
||||
---
|
||||
|
||||
General contribution guidelines can be found [here](https://github.com/larshp/abapGit/blob/master/CONTRIBUTING.md).
|
||||
General contribution guidelines can be found [here](https://github.com/abapGit/abapGit/blob/master/CONTRIBUTING.md).
|
||||
|
||||
How to submit a pull request:
|
||||
|
||||
|
|
|
@ -26,4 +26,4 @@ You can use the exit `CREATE_HTTP_CLIENT` to implement a different authenticatio
|
|||
|
||||
## Security considerations
|
||||
|
||||
abapGit intentionally does not provide a way to store login data across sessions. This is because SAP systems are multi-user-systems and since abapGit is mostly used by developers on shared development systems who have extensive authorizations any approach to store passwords runs the risk of getting abused. On local single user systems you can easily implement the exit mentioned above to permanently store the login data in a RFC destination. Otherwise a password manager is the recommended approach to store login data. (See discussion in [#3798](https://github.com/larshp/abapGit/issues/3798))
|
||||
abapGit intentionally does not provide a way to store login data across sessions. This is because SAP systems are multi-user-systems and since abapGit is mostly used by developers on shared development systems who have extensive authorizations any approach to store passwords runs the risk of getting abused. On local single user systems you can easily implement the exit mentioned above to permanently store the login data in a RFC destination. Otherwise a password manager is the recommended approach to store login data. (See discussion in [#3798](https://github.com/abapGit/abapGit/issues/3798))
|
||||
|
|
|
@ -9,7 +9,7 @@
|
|||
},
|
||||
"repository": {
|
||||
"type": "git",
|
||||
"url": "git+https://github.com/larshp/abapGit.git"
|
||||
"url": "git+https://github.com/abapGit/abapGit.git"
|
||||
},
|
||||
"devDependencies": {
|
||||
"@abaplint/cli": "^2.54.0",
|
||||
|
|
Loading…
Reference in New Issue
Block a user