- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Distribute software tokens
Good afternoon,
We have not used software tokens before in our organization. I have loaded a number of software tokens into our RSA environment. Then I created a new profile in the Software Token Profiles screen with which the tokens can be rolled out. I have opted for Dynamic Seed Provisioning.
As a test I have distributed a software token. The RSA console then refers the users to https://<our rsa server>:7004/ctkip/services/CtkipService, when I try to open this page I get a certificate error message first and then I get a page not reachable error.
Do we miss something in our environment to roll out software tokens?
Regards,
Mark
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
My suggestion would be to read about the WebTier option and deploy a web tier so you can have a Certificate that is not an RSA Self Signed Cert (the first Cert error/complain) and the ability to use a standard port 443 which is probably the second issue you are having
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
J. Verhoeksā,
I've moved your question regarding RSA SecurID software tokens and dynamic seed provisioning to the RSA SecurID Access space where it will be seen by the product's support engineers, other customers and partners. Please bookmark this page and use it when you have product-specific questions.
Alternatively, from the RSA Customer Support page, click on Ask A Question on the blue navigation bar and choose Ask A Product Related Question. From there, scroll to RSA SecurID Access and click Ask A Question. That way your question will appear in the correct space.
Regards,
Erica
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
My suggestion would be to read about the WebTier option and deploy a web tier so you can have a Certificate that is not an RSA Self Signed Cert (the first Cert error/complain) and the ability to use a standard port 443 which is probably the second issue you are having
