Announcements

SecurID® Discussions

Browse the SecurID discussion board to get product help and collaborate with other SecurID users.
EricZoeckler
Contributor
Contributor

Failed browsing to SC

Jump to solution

I'm setting up new Securid Appliance 130.  Completed the quick setup but can't browse to the security console with current IE or Firefox browsers.  Is there a recommendation for browser/version and settings?

Eric Zoeckler
0 Likes
1 Solution

Accepted Solutions
EdwardDavis
Employee
Employee

What version of Authentication Manager ?

 

What is the specific URL you are trying (please do not post real machine names or addresses here) ?

 

the URL is https://name.of.box:7004/console-ims 

or the shortcut URL

https://name.of.box/sc  (which redirects to the first URL I posted)

 

 

What specific error message in browser ?

 

If this is version 8.4.0.0.0 then all that is needed is TLS1.2, and accepting a self-signed certificate. Browsers and security settings often warn about connecting to a system with self-signed certificates because in the 'outside world' that might be risky, but for Auth Manager, it is not a vulnerability... but may be marked as one, and might be blocked by security systems checking for 'well known' certs..

 

If this is version 8.1.0.0.0 (base) then that can only do SSL, and that is definitely blocked by most browsers today, you need to set the browser to allow SSL3.0 for connection. 

View solution in original post

3 Replies
EdwardDavis
Employee
Employee

What version of Authentication Manager ?

 

What is the specific URL you are trying (please do not post real machine names or addresses here) ?

 

the URL is https://name.of.box:7004/console-ims 

or the shortcut URL

https://name.of.box/sc  (which redirects to the first URL I posted)

 

 

What specific error message in browser ?

 

If this is version 8.4.0.0.0 then all that is needed is TLS1.2, and accepting a self-signed certificate. Browsers and security settings often warn about connecting to a system with self-signed certificates because in the 'outside world' that might be risky, but for Auth Manager, it is not a vulnerability... but may be marked as one, and might be blocked by security systems checking for 'well known' certs..

 

If this is version 8.1.0.0.0 (base) then that can only do SSL, and that is definitely blocked by most browsers today, you need to set the browser to allow SSL3.0 for connection. 

V8.4  Found that it failed due to needed DNS confuration.  Did not respond to https://ip:7004/sc but worked with FQDN with the DNS set correctly.  Thank you for your response.

Eric Zoeckler

OK that makes sense. The Operations Console specifically will allow IP only or name, because the Ops Console is where you can change DNS server settings, so in case name resolution is lost, we allow IP only to go in and fix it. But the Security Console is fussier, and if you use the IP, it will try to reformat the URL to name and if DNS is not consistent, could have issues.