Certificate Authentication for REST API access

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Certificate Authentication for REST API access

L3 Networker
I am having a little trouble with getting this setup, and I was wondering if there is anyone that might have some insight. I have a dev environment where I am testing this and right now authentication into the web console is through LDAP. From reading about how to setup certificate authentication for the Rest API, I need to toggle Certificate Authentication checkboxin Platforms, then update IIS SSL settings for Aperture and VEDAdmin to Require SSL certificates. The problem with doing this is that it locked me out of the web console immediately. I did not even have an option to put in user/pass credentials. Had to run a query on the DB to clear that. Is there any way to do certificate authentication to get a bearer token for API calls without affecting access to the web console?.
11 REPLIES 11

L1 Bithead

Make sure youre reading the right documentation for how to configure certificate auth for the API.

 

 It sounds like you followed the doc for configuring it for the Web Console. You do not want to modify Aperture or VEDAdmin IIS settings. The IIS changes should be limited to VEDAuth.

L1 Bithead

Make sure youre reading the right documentation for how to configure certificate auth for the API.

 

 It sounds like you followed the doc for configuring it for the Web Console. You do not want to modify Aperture or VEDAdmin IIS settings. The IIS changes should be limited to VEDAuth.

L2 Linker

Hi dghort, are you trying to enable certificate authentication for Web Console or REST API? 

 

L3 Networker
I guess the main question is the URL in the call correct? ''https://tpp.domain.com/vedauth/authorize/certificate The more I read the more it looks like I have to have the web console certificate authentication set up to use this one. I have all of the API Authentication items checked that are necessary.

L3 Networker
I guess the main question is the URL in the call correct? ''https://tpp.domain.com/vedauth/authorize/certificate The more I read the more it looks like I have to have the web console certificate authentication set up to use this one. I have all of the API Authentication items checked that are necessary.

L3 Networker
Additional screenshots for VEDAuth SSL Settings and Venafi site IIS Certificate Mapping

L3 Networker
Well I managed to get to the point where I am no longer getting the Certificate Authentication working. Now it looks like a permissions issue. Getting this Invoke-RestMethod : 403 - Forbidden: Access is denied. Server Error 403 - Forbidden: Access is denied. You do not have permission to view this directory or page using the credentials that you supplied. Not sure what on the certificate might be a problem. Is there a specific scope I need to usein order to make this work?

L3 Networker
The good news is that I have figured out my own problem. I am posting it here for reference in case anyone else runs into the problem. Somehow the Venafi Operational Certificate that was created from our internal CAafter the initial install was in place in the Trusted Root store in addition to the Personal store. I essentially moved that to the Intermediate store and it started producing a token. This main issue is that the Trusted Root store should ONLY contain self-signed certificates. Having a signed certificate in the Trusted Root store caused my issue. Running this script in Powershell will find all certificates that are not self-signed which you can then move accordingly. Get-Childitem cert:\LocalMachine\root -Recurse | Where-Object {$_.Issuer -ne $_.Subject} | Format-List * | Out-File 'c:\computer_filtered.txt'

L3 Networker
The good news is that I have figured out my own problem. I am posting it here for reference in case anyone else runs into the problem. Somehow the Venafi Operational Certificate that was created from our internal CAafter the initial install was in place in the Trusted Root store in addition to the Personal store. I essentially moved that to the Intermediate store and it started producing a token. This main issue is that the Trusted Root store should ONLY contain self-signed certificates. Having a signed certificate in the Trusted Root store caused my issue. Running this script in Powershell will find all certificates that are not self-signed which you can then move accordingly. Get-Childitem cert:\LocalMachine\root -Recurse | Where-Object {$_.Issuer -ne $_.Subject} | Format-List * | Out-File 'c:\computer_filtered.txt'

L4 Transporter
Thank you for following up with your findings @dghort !

L4 Transporter
Thank you for following up with your findings @dghort !
  • 202 Views
  • 11 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!