Can't open a support case

[ImreBone1]

I get the message "You don't have access. Please contact RSA Administrator" after pressing submit.

Seems like others have had this same issue: https://community.rsa.com/message/917608 

Also, it would be better if the portal notified users they can't submit cases before they would type in a full technical issue description and not after that.

[_EricaChalfin]

Imre Bone‌,

I am sorry to hear that you are having an issue with opening a support case online.  

It looks like your risk-based authentication methods (i.e. security questions and/or On-Demand Authentication) have not yet been configured.  To do this, you must visit the Self-Service Console and configure one or both of the methods.  You should then be able to access Case Management.

Regards,

Erica

[_EricaChalfin]

Imre Bone,

Please let me know if you are still having an issue.

Regards,

Erica

[ImreBone2]

I've added both risk based authentication methods to my account.

I get the below error when trying to access https://rsaportal.force.com/customer/apex/CP_Select_Case?sfdc.tabName=01r70000000Q8sD 

[_EricaChalfin]

Imre Bone,

Thank you for the additional information.  The error you are seeing is because of a discrepancy in your account in our backend systems.  I opened a ticket with out intenral IT department to address it.  Our tracking number is RSALINK-10371.

I will let you know as soon as the issue is resolved.

Regards,

Erica

[_EricaChalfin]

Imre Bone‌,

Please try loggin in again and try to open a support case.

Regards,

Erica

[ImreBone2]

I still get the same Single Sign-On Error.

[_EricaChalfin]

Imre,

My apologies that you are still having an issue.  I am working with IT to address it in RSALINK-10371. Please give me a few hours to get more information.  In the mean time you can always open a case by contacting RSA Support.

Regards,

Erica

[_EricaChalfin]

Imre Bone‌,

Thank you for taking the time yesterday to resolve your issue.

Regards,

Erica

[ImreBone2]

Just to confirm: my issue was solved after re-registering my account at the RSA Registration Portal .