Hello,
I was wondering if anyone ever tried to update an existing Organisation to use the legacy protocols via PowerShell or the API.
It's no problem to set the "Allow for usning legacy authentication protocols" via the GUI.
But i couldn't find anything doing this via PowerShell or the API.
For the API I always get the error that some settings aren't allowed when using modern authentication if I try to update an organisation.
Kind Regards
Sven
-
- Service Provider
- Posts: 5
- Liked: 1 time
- Joined: May 03, 2021 9:48 am
- Contact:
-
- Product Manager
- Posts: 5797
- Liked: 1215 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: Update existing Organisation with legacy protocols via Powershell or API
Do you have a copy/paste of the error you receive?
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
GitHub: https://github.com/nielsengelen
-
- Service Provider
- Posts: 5
- Liked: 1 time
- Joined: May 03, 2021 9:48 am
- Contact:
Re: Update existing Organisation with legacy protocols via Powershell or API
Hi,
I'm unsing https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=50
with applicationCertificate. The organisation gets created but without the "Allow for usning legacy authentication protocols".
The error I'm always getting after I try to extend the json file is:
message": "Parameter cannot be specified: XXX. Invalid parameter set for modern authentication.."
So I'm not sure what really creates this setting. Looks like the example isn't.
I'm unsing https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=50
with applicationCertificate. The organisation gets created but without the "Allow for usning legacy authentication protocols".
The error I'm always getting after I try to extend the json file is:
message": "Parameter cannot be specified: XXX. Invalid parameter set for modern authentication.."
So I'm not sure what really creates this setting. Looks like the example isn't.
Who is online
Users browsing this forum: Google [Bot] and 21 guests