- Community Home
- >
- Networking
- >
- Wireless
- >
- M and MSM Series
- >
- Re: Wildcard certificate on MSM causes asterisk in...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-17-2013 12:55 PM
тАО01-17-2013 12:55 PM
Everything I read indicates that wildcard certificates (*.domain.com) are not supported on the MSM. Is this still the case? Is there a workaround for this problem?
When a user connected to an Access Controlled VSC opens a web browser, (when using a wildcard certificate) they are re-directed to http://*.domain.com:8080/index.asp (where domain.com is our domain). If you manually type the interface IP address of the controller in place of *.domain.com, then the correct authentication page loads.
The same is true once a user is authenticated. Normally a session pop-up is supposed to appear. However, the URL is wrong (contains the asterisk instead of the host name of the controller). Han anyone run into this before? Any help is much appreciated.
I am going to check DNS as well, but I figure the controller (since it is intercepting DNS) would be able to make it's own URL with a wildcard certificate. Please let me know if there is a workaround for this. Any help is greatly appreciated.
Thank you!,
--John
Solved! Go to Solution.
- Tags:
- certificate
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-17-2013 02:05 PM
тАО01-17-2013 02:05 PM
SolutionAs far as I know this is not supported. I recommend my customers to use e.g. http://www.startcom.org/ to generate a free official certificate for the controller guest portal (1 free cert per domain I believe)
Remember to include the CRL URL of the certificate in the unauthenticated user ACL on the controller, so new guest systems are able to verify and resolved the CRL of the certificate, otherwise the browser can take a long time before it shows the secure login page (trying to check the CRL, but it fails since blocked by the controller)
best regards,Peter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-05-2013 11:31 AM
тАО02-05-2013 11:31 AM
Re: Wildcard certificate on MSM causes asterisk in DNS redirect
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-28-2014 08:14 AM
тАО05-28-2014 08:14 AM
Re: Wildcard certificate on MSM causes asterisk in DNS redirect
That is NOT SOLVED. The provided solution is just a workaround.
This is a SERIOUS bug of the MSM760 software. The redirect hostname should be configurable, not hardcoded in the SSL certificate, since a valid (and paid) wildcard certificate should be fine.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-20-2014 12:07 AM - edited тАО06-20-2014 12:08 AM
тАО06-20-2014 12:07 AM - edited тАО06-20-2014 12:08 AM
Re: Wildcard certificate on MSM causes asterisk in DNS redirect
I have been using wildcard certs on the web management interface since back to at least 5.3.6 software. It works flawlessly. Installed from a PFX file and using a split DNS namespace.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-11-2017 07:55 PM
тАО06-11-2017 07:55 PM
Re: Wildcard certificate on MSM causes asterisk in DNS redirect
This is also affecting us. Redirect hostname should be configurable!