• Resolved toad78

    (@toad78)


    Greetings!
    For over a week now I’ve been fighting with getting this plugin to work. While we have set up the correct ID/Secret information, the Authorisation (misspelled on the plugin) still says:

    “You need to save settings with a valid Tenant ID, Client ID and Client Secret before you can proceed.”

    We even attempted a test on a Contact form to no avail.

    Not sure what to do. We’ve changed the keys a few times and still receive that same message. If it helps, we’re currently testing on a staging environment and know that once we go live we may have to change the keys again for the changed domain. But nonetheless, we should at least have something working at this point with the correct information already inputted.

    Thank you.

Viewing 6 replies - 1 through 6 (of 6 total)
  • @toad78 So there’s no misspelling that I can see (I’m UK not USA, but the error messages from Microsoft’s API that get displayed are in American English). However, being a displexic (or is that dyslexic), I could be in ignorant bliss.

    As to the technical issue, I suspect it’s because the Client Secret you’re putting in is actually the ID of the secret, and not the secret itself. There are two values generated by Microsoft in the tokens area of the Azure GUI – you want the value, not the ID.

    • This reply was modified 2 years, 3 months ago by edwardcross.

    @toad78 actually, just tested and the client secret doesn’t make any different to that message being displayed or not. It’s something to do with the client ID (note this is difference to the client secret ID) or tenant ID.

    The client id is effectively the application id for the app you create to handle the authorisation process within Azure Active directory. As I understand it, this client/application ID has to be hosted within the same tenancy. If you have created an app using a different tenancy to the tenant ID you are putting in the tenant ID box of the plugin, you may way get an error.

    If that isn’t the issue, it could be you are using a tenancy that isn’t a paid for Office 365 account. Microsoft doesn’t support free Office/Hotmail etc. accounts with their Graph Mail API (or at least last time I checked they didn’t).

    I’m out of ideas if nether of these resolve things. Google is your friend otherwise.

    Thread Starter toad78

    (@toad78)

    Tenancy = domain URL, correct? Because the primary domain for the SMTP Office account is different than the staging site URL, which is what I suspected in the first place.

    • This reply was modified 2 years, 3 months ago by toad78.

    @toad78 can you send me a screenshot of your settings page via my website’s contact form (https://crossconnected.co.uk/contact-us/)? Don’t post it here, as whilst the tenant ID and client ID aren’t necessarily bad to share publicly, it’s advisable to not broadcast them widely. Don’t send me the client secret either, that’s secret for a reason. However, a screenshot should just show dots for the client secret entry.

    Cheers,

    Ed

    @toad78 I’m going to close this now, as having discussed via email, the issue is more to do with the fact Ninja Forms wasn’t working for you, rather than the invalid tennant ID. There are several open tickets relating to contact form issues which I am still trying to resolve, so I’m marking this resolved to avoid duplication.

    • This reply was modified 2 years, 3 months ago by edwardcross.
    Thread Starter toad78

    (@toad78)

    Thank you for your time, edwardcross.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Authorisation Issue: You need to save settings with a valid Tenant ID…’ is closed to new replies.