OK so I've kind of gone with the first idea,

If I click my new section: http://local.testsite01/umbraco/#/mySection ,and when I load my treecontroller and I don't have a AccessToken, I hide all the options and just provide a 'Connect' option, like:

 protected override MenuItemCollection GetMenuForNode(string id, FormDataCollection queryStrings)
    {
        MenuItemCollection collection = new MenuItemCollection();

        if (string.IsNullOrEmpty(_accessToken))
        {
             collection.Items.Add(new MenuItem("auth", "Connect"));
            return collection;
        }

This redirects to

~/App_Plugins/myApp/BackOffice/Catalog/oAuth.html

So on the load of that view the angular posts off to a backend controller which then starts the process. After the standard oAuth calls, it then redirects me back to the root of my Section: http://local.testsite01/umbraco/#/mySection

The TreeController rebuilds itself, but this time it's got a AccessToken so can build to 'real' tree/ menu.

I'll need to consider if/ when the access token expires. I'll prob redirect to the root and ask for a reconnect but it's not the best user experience.

Hi Again,

Some more ramble...

So I've decided to change the way I manage the oAuth process. I'm now triggering the process from the click of the new section, I've done this by adding the following to the dashboard.config file:

<section alias="ecommerceOAuthStartup">
<areas>
  <area>ecommerce</area>
</areas>
<tab caption="Welcome">
  <control showOnce="true" addPanel="true" panelCaption="">
    ../App_Plugins/myApp/Backoffice/Dashboards/Auth.html
  </control>
</tab>

Auth.html, loads it's controller which then on the load kicks off the oAuth process if it doesn't have a Access Token. When it's complete it redirects back to the root. Main drawback to this approach is you get a flicker when the page is refreshing with the token. However it means every catalog tree doesn't have to deal with it.

is working on a reply...