When you create keys in Laserfiche for OAuth 2.0 authentication, it gives you a JWK JSON string. Why is this not an option when we create the Web Service Connection?
Chad,
Thank you for the feedback, and we are working on implementing additional OAuth 2.0 types for Web Service Connections. Feel free to reach out directly if you'd like to discuss this more in depth - I'm pretty sure you have my email.
Thanks,
Andrew
I ended up finding the article below which shows you how to use the Long Lasting Auth key as an OAuth 2.0 Configuration. But the terminology is misleading since when you create a key it says either OAuth, Long Lasting, or Basic. I would expect the terms to match up on both ends; where we create the creds and where we use them.
There was one flaw in the doc though, it has the wrong Token Endpoint URL in the second screenshot. Google AI cleared that up for me.
https://signin.laserfiche.com/oauth/Token is the correct token endpoint. What did Google tell you to use?
That is what Google told me to use, because the documentation lists both https://signin.laserfiche.com/oauth/Token and https://signin.a.clouddev.laserfiche.com/oauth/Token without explaining which to use. I needed Google to clear it up.
Definitely not clouddev. We'll clean it up.