Sergei Sergeev

Hi Sumen, I see your request, currently I'm lack of time to check your scenario, please expect some delay in answer. Sorry for inconvenience.

Hi, could you tell me what exact issue do you have? What is the error code or maybe a stack trace?

If pnp-auth works, then sp-request also should work. You could try inspecting HTTP requests to see the difference in the headers and authentication. Also, which kind of authentication do you...

Does it work when you use a Client ID and Secret ID? Also maybe it doesn't work because legacy auth is disabled for you? You can try executing [Get-SPOTenant](https://docs.microsoft.com/en-us/powershell/module/sharepoint-online/get-spotenant?view=sharepoint-ps) and...

When you use bearer tokens, then it's OAuth, with username\password it's cookie based auth, and it looks like it doesn't work with new taxonomy REST endpoint (`_api/v2.1/termStore`). Actually, it's just...

No, except using OAuth type of authentication. Alternatively, if you need a username and passwords and cannot get rid of it, you can implement [ROPC](https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth-ropc) flow with a regular Azure...

Yeah, it makes sense, thanks for the suggestion! Will work on this feature when I finish upcoming fast-serve changes.

It looks like it's a common problem for nodejs 17 and many other packages, which rely on OpenSSL internally. I found the only workaround is to set ``` export NODE_OPTIONS=--openssl-legacy-provider...

Hi, it's very difficult to diagnose the root cause of such errors. Usually, it happens when NTLM v2 was enabled, but the library already supports NTLM v2. Maybe the issue...

Please also check that you don't have Kerberos setup. Kerberos isn't supported.