Open garycnew opened 3 years ago
The username and password is expected to be global to the whole API. It's not domain-specific.
There were requests that were to save the username/password per domain, but it was not implemented yet. And I don't see any urgent such demands yet.
Neil,
The _readaccountconfmutable() function already accepts the underscore (\) character.
It would just be a matter of permitting the dot (.) and hyphen (-) characters.
Until such time as the requested functionality is added, I have implemented the following workaround, in the dns_ispman.sh api, that seems to work perfectly (as long as the words "hyphen" or "dot" are not used in the fulldomain):
fulldomain=$1
txtvalue=$2
domainname="$(echo ${fulldomain#_acme-challenge.} | sed "s/\-/_HYPHEN_/g" | sed "s/\./_DOT_/g")"
ISPMan_Username="${ISPMan_Username:-$(_readaccountconf_mutable ISPMan_${domainname}_Username)}"
ISPMan_Password="${ISPMan_Password:-$(_readaccountconf_mutable ISPMan_${domainname}_Password)}"
I believe I have pretty much everything sorted out with the dns_ispman.sh api including successful Wildcard SAN Cert Creation and Multi-User/Multi-Domain Functionality. What is the process for submitting an api for consideration to be included with the acme.sh script?
Respectfully,
Gary
Neil,
I believe I've stumbled upon an issue where account.conf SAVED_ variables with dot or hyphen are incomparable with the _readaccountconf_mutable() function. The variables appear to get truncated at the dot or hyphen demarcation.
Examples:
Implemented Code:
Resulting Account.conf Variable:
Implemented Code:
Resulting Account.conf Variable:
As each ISPMan managed domain uses a separate username/password pair, we'd like to be able to use multiple SAVED_ variables, based on their respective domain name, to automate the renewal process.
Is this functionality something you can and feel is worth implementing within the acme.sh script or should I deal with it programmatically with the api?
Respectfully,
Gary