You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the solution you'd like
In the GUI, when doing Generate Certificate Signing Request, there are optional fields for Subject Alternative Names, up to 4 of them. The module ome_application_certificate does not have support for these fields
Describe alternatives you've considered
Manually generate the CSR and then upload with resulting cert with the Ansible module
Additional context
I use a VIP for my OME-M environment, so if I use the Ansible module using the VIP name, it does not also include the chassis DNS name. DellGroup1.domain.com for the VIP but also need to add DellGroup1Chassis1.domain.com for the actual Chassis that is currently the Lead
Community Note
Please vote on this issue by adding a 👍 reaction
to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions,
they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
The text was updated successfully, but these errors were encountered:
@MallocArray, thank you for submitting the feature request. I have added it to the backlog and we will accordingly prioritize it for our future releases.
Describe the solution you'd like
In the GUI, when doing Generate Certificate Signing Request, there are optional fields for Subject Alternative Names, up to 4 of them. The module
ome_application_certificate
does not have support for these fieldsDescribe alternatives you've considered
Manually generate the CSR and then upload with resulting cert with the Ansible module
Additional context
I use a VIP for my OME-M environment, so if I use the Ansible module using the VIP name, it does not also include the chassis DNS name. DellGroup1.domain.com for the VIP but also need to add DellGroup1Chassis1.domain.com for the actual Chassis that is currently the Lead
Community Note
to the original issue to help the community and maintainers prioritize this request
they generate extra noise for issue followers and do not help prioritize the request
The text was updated successfully, but these errors were encountered: