Adding authorisation options for API access

- ldap currently the only supported method
adding authorisation options for local repositories
  - ldap groups per repo
This commit is contained in:
bpiraeus
2022-03-13 16:07:21 -07:00
committed by André Roth
parent ab18da351d
commit 836137f15d
14 changed files with 358 additions and 66 deletions
+17 -2
View File
@@ -341,6 +341,7 @@ The legacy json configuration is still supported (and also supports comments):
// Storage. First, publishing endpoints should be described in the aptly
// configuration file. Each endpoint has its name and associated settings.
"AzurePublishEndpoints": {
<<<<<<< HEAD
// // Endpoint Name
// "test": {
@@ -392,12 +393,26 @@ The legacy json configuration is still supported (and also supports comments):
// // See: Azure documentation https://docs.microsoft.com/en-us/azure/storage/common/storage-configure-connection-string
// // defaults to "https://<accountName>.blob.core.windows.net"
// "endpoint": ""
}
},
// Authorization for repos may be configured for ldap groups (and is extensible for others),
// default is no authorization.
"Auth": {
// // auth type, only supports ldap currently
// "authType: "",
// // auth server to use (eg. ldaps://ldap.example.com)
// "server\": "",
// // DN for ldap searches
// "ldapDN\": "",
// // ldap filter
// "ldapFilter": "",
// // enable secureTLS, default is off
// "secureTLS": false
}
// End of config
}
## PACKAGE QUERY
Some commands accept package queries to identify list of packages to process.