EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB248664: "403 - Forbidden: Access is denied" error when attempting to login using MicroStrategy Mobile and MicroStrategy Certificate Server 9.x and 10.x


Community Admin

• Strategy


When a user attempts to login using MicroStrategy Mobile ASPx with enabled Certificate Server, the following error message is shown and the user is unable to proceed: "403 - Forbidden: Access is denied" The issue is only reproduced when the Web Server requires a client certificate to be provided by the client that attempts to log in. IIS application logs reveal the exact HTTP error code is 403.13 for the request in question.

SUMMARY
When a user attempts to login using Strategy Mobile ASPx with enabled Certificate Server, the following error message is shown and the user is unable to proceed:


"403 - Forbidden: Access is denied"

The issue is only reproduced when the Web Server requires a client certificate to be provided by the client that attempts to log in. IIS application logs reveal the exact HTTP error code is 403.13 for the request in question.
CAUSE
403.13 HTTP status describes "Client certificate revoked". One possible cause for this error is that the certificate revokation list (CRL) is out of date and needs to be recreated. By default, the validity period is 365 days and is extended each time a certificate is revoked. However, if no certificates have been revoked within one year, the CRL expires and IIS is unable to accept any client certificate.
ACTION
Check if the certificate revokation list (.crl) has a next update date older than the current day. IIS will reject every client certificate when the CRL is out of date, thus returning 403.13 errors to clients attempting to connect. In order to recreate the CRL perform the following steps:
1. Backup or delete the existing CRL file in the Certificate Server deployment folder
2. Activate a new CRL using the following URL API:

ASP: https://fully_qualified_domain_name:port/CertificateServer/asp/CertificateAdmin.aspx?action=RevokeCertificate&serialNumber=(dummy_number_here)


Comment

0 comments

Details

Knowledge Article

Published:

April 7, 2017

Last Updated:

April 7, 2017