This message was deleted.

About 3 months ago, I was told it doesn't yet. However, I did not investigate the why behind it.

I was wondering about this because I can find no information on it. All my experience to date with quite a few Imprivata deployments has all been on prem.

I know nothing of Imprivata, but if it points to Storefront, you could still do cloud but keep Storefront on-prem. Still have to have Storefront for thin clients and other use cases so not unheard of

Yes, but that means managers need to be aware because if you have SF, you probably want two, and then that probably means you should keep a NetScaler or two around also, etc. Imprivata behaves like they are protecting gold bars at Fort Knox; getting any information out of them is almost impossible, unless you are the customer (and as a consultant this can be quite annoying when you just need something simple like a compatibility matrix).

correct, keeping Storefront/NetScaler on prem is not uncommon

I was working on an Azure POC with DaaS about 3 months ago. They wanted to use Imprivata in the way that you described. At that time, we kept the SF server and Gateway in-house. But then used everything else in the cloud. But yea, it was hard to get the information from the vendor.

last i talked to Imprivata, they still required StoreFront integration on a store for something so I would maybe assume you will need to keep that around for Tap N Go purposes.

It needs storefront. It’s a trigger the same as thin clients often are. It uses a specific auth method on storefront which workspace doesn’t have. Most environments running imprivata are typically looking for the local resiliency of storefront and netscaler anyway - if you get stuck with contacts, I have a couple of local (Australia) contacts who are very helpful. DM me if you need

Thanks @Oz Zy, @James Kindon and everyone else on this input. This is exactly what I suspected was the case, but I could not get anyone at Imprivata to talk to me (although I had the customer open up a case with them and we have a meeting next week on this).

Imprivata barely even works with nfactor and advanced policy, it needs a lot of custom config that you aren’t going to be able to do with gateway service. Ran into a ton of issues doing a 13.1 migration on netscaler.

Imprivate shines when it's architected simply and as per it's original design, get's a bit quirky when you try and square-peg-round-hole it