Managing Several SharePoint Sites

[dboyd-invitoep]

I have 12 SharePoint sites synced, each with its own systemd (--user) file which start when I log into the system. My employer's O365 environment requires re-authentication pretty frequently and this is a major hassle. Each of my SharePoint sites has its own onedrive instance running and when one of them has its authentication expire, it's not always clear to me which are still functioning and which have expired. I then go through this painstaking process where I stop each onedrive instance (systemctl --user stop onedrive_<sharepoint_site>), reauth (onedrive --confdir ~/.config/sharepoint/<sharepoint_site> --reauth) log in, paste the response URL, and then restart the client (systemctl --user start onedrive_<sharepoint_site>)

I can't even figure out how to automate this because it requires interacting with a browser. There has to be a better way!

[abraunegg]

@dboyd-invitoep

I can't even figure out how to automate this because it requires interacting with a browser. There has to be a better way!

Pick 1 of the SharePoint sites to be your 'primary' and symbolically link the other 11 sites 'refresh_token' to the primary one.

This way, when the re-authentication is required, you are only doing it once, for all.

This should lessen the pain of trolling through logs, and re-auth each individual configurations - you only need to do this once on the 'primary'.

[dboyd-invitoep]

great suggestion -- one other quick question, is there any way to make the client less verbose? It would be nice if it would just post most messages to journalctl and not to the GNOME notification center. I have to dismiss warnings in my notification center pretty much constantly.

[abraunegg]

Please read the documentation

[danjboyd]

Quick question for you--I believe the behavior of the microsoft oauth servers is to issue a new refresh token every time you request an access token. I'm seeing in onedrive.d where you are writing the new refresh token to disk. And I believe the std.file.write function will overwrite the target file if the file is a symlink as you suggested (and does so atomically). I have 10 sharepoint sites and one onedrive-for-business site configured on my system and everything is symlinked to the refresh_token in the onedrive's confdir.

So, when I log onto my machine, systemd starts all 11 of these processes more-or-less simultaneously, which should cause the refresh_token file in my onedrive's confdir to get re-written 11 times in almost immediate succession. How does this not cause some of the instances to read a refresh_token from disk while another instance is writing? Even with atomic writing, that could cause issues, I would think...?

To be clear, nothing is wrong and this appears to be working smoothly, but I'm not sure I understand why it is :)

[abraunegg]

Because the writing to the disk only occurs if required. The token is held in memory and is updated / compared there first.