Login using SharePoint App-Only instead of AAD App-only?

[vamsi981]

Hi @estruyf ,

Is it Possible to use SharePoint APP-only Add-In Client id and Secret Instead of M365(Azure based) Client id and Secret, where the scope is only limited to particular Site Collection Instead of entire SharePoint tenant level.

[vamsi981]

In our Scenario, we are using SharePoint add-in for connecting to a Site Collection for publish/creating Pages. with the package can we use the Same for publishing pages using M365 CLI?

[gkohen]

Hi @estruyf. First of all thank you for this top notch library. Looks like it got lots of potential. On the question of @vamsi981
above, please let us know if we can contribute and it might be as simple as delegating a new auth mode(client/secret) on this class or you see additional complications.
Thanks!

[estruyf]

@gkohen contributions are more than welcome! Haven't been using doctor for a long time, so contributions are helpful to get it better by people who actually use it.

[gkohen]

No worries @estruyf. On the specific issue of the technical question raise by @vamsi981, do you see any issue with the current implementation being able to create pages if we contribute a client/secret auth support?
On a side note related to your last comment, do you know is this tool being actively maintained and used by the community?

[estruyf]

It uses the CLI for Microsoft 365, which is actively maintained. This library is a wrapper around that dependency, with the ability to understand how to translate the markdown content to SharePoint Pages.

We need to check if the CLI can be used with client/secret auth. If it does, it would be an easy way to be implemented it.

Happy to also bring some new life in the library, as it has a huge potential for teams.

[bentolor]

In my environment a login using user/pass leads to an Error: invalid_client: 7000215: AADSTS7000215: Invalid client secret provided.. But I also got a client secret.

• localm365 uses an old m365 v3.x version, which doesn't seem to understand client secrets
• a current m365 allows me to successfully login using the following command:

m365 login --authType secret --secret "secret" --tenant "xxx" --appId "xxxx"

Any reasons for the really outdated version of the bundled m365, @estruyf ?

[bentolor]

Ok: With my limited understanding I hacked an updated version to use client secret authentification, but eventually I received this feedback from m365:

Error: SharePoint does not support authentication using client ID and secret. Please use a different login type to use SharePoint commands.

Not sure if I'm on the same page as the others on this thread, but it seems I'm not able to go that path.

[gkohen]

Digging deeper into the PNP CLI it seems like there is an actual blocker on the Microsoft service API:
pnp/powershell#277