nodemailer/wildduck
1
1
Fork 0
mirror of https://github.com/nodemailer/wildduck.git synced 2025-09-09 14:46:55 +08:00
Code Issues Projects Releases Packages Wiki Activity

updated docs

Browse source
This commit is contained in:
Andris Reinman 2021-05-20 11:48:01 +03:00
parent a468bee601
commit d52adcebcf
1 changed files with 8 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
docs/api/openapi.yml
View file

@ -919,10 +919,11 @@ paths:
example: example.com
- name: altNames
in: query
description: Match `query` value against SAN as well (by default checks only registered server names)
description: Match `query` value against SAN as well (including wildcard names)
schema:
type: boolean
example: false
example: true
default: false
- name: limit
in: query
description: How many records to return
@ -955,7 +956,11 @@ paths:
tags:
- Certs
summary: Create or update TLS certificate for server name
description: Add a new TLS certificate for a server name or update existing one. You can add a single certificate for each server name but SAN names are supported as well. For example you can add a sertificate for "mydomain.com" that has a "\*.mydomain.com" SAN set and it would be used for requests that do not have it's own server name registered but match the SAN value.
description: >
Add a new TLS certificate for a server name or update existing one. You can add a single certificate for each server name but SAN names are supported as well.
For example you can add a sertificate for "mydomain.com" that includes "\*.mydomain.com" in SAN and the same certificate would be used for requests that do not have it's own server name registered but match the SAN value.
> NB! you must ensure yourself that the `servername` value is actually listed in certificate's common name or SAN as WildDuck is going to use this certificate regardless.
operationId: updateTLSCertificate
requestBody:
description: Add a new TLS certificate for a server name or update existing one