Home > Software engineering >  Using different client certificates for different routes
Using different client certificates for different routes

Time:11-24

I'm working with an SSL application and I would like to read data from two client certificates. When a user comes to my site he chooses a certificate and enters a pin, which get cached and used by subsequent requests until Chrome (et al) gets restarted.

Any ideas on how to prompt the user for a certificate for a second time on the same site?

Regards.

CodePudding user response:

A solution that has satisfied my need was to bind the app on two https ports in IIS config. Works on IIS Express also.

More info: I am making two ajax requests on routes that are matched by a single <location> tag web.config. This location requires a certificate, which means user gets prompted when accessing them. Since these two ajax calls go to different ports, user gets prompted on the second ajax call too.

Knowing how to clear the cache would have been nicer for other use cases, because restarting Chrome is not something I would ask my users to do.

  • Related