unable to connect to mingle after receiving bearer token

Hi guys,

I was trying out some example How to call an ION API in particular for Oauth2 Authorization Code grant on which I was able to utilise the bearer token generated.

I set all my authorise app as per given steps incognito mode and run my testing on postman.

When I tried to access my mingle after manually, I got the following error

If I was logged prior to testing on postman, I wouldnt get such error. Any thoughts?

Find more posts tagged with

ION API Gateway

Accepted answers

unknown

Can you please confirm if the Tenant used for testing in Postman and the Tenant that you are accessing via Ming.le are the same?

If they are different, then it may explain why you see this error as the token is associated with your default browser session. Remember that, calling an ION API via Postman also invokes your default browser for the initial authentication and hence might clash with the new tenant you may be accessing in Ming.le. Default token validity is 2 hours. One option is to see, if you login to Mingle at least after 2 hours of testing via Postman and verify if the error goes away. You can also set the token validity to a minimum of 15 mins in your Authorized app settings, which might reduce the wait time.

Another suggestion: you mentioned that you tried the incognito mode. Instead can you try the login in Ming.le portal via a completely different browser (like IE or Firefox. Even though they may not be officially supported, at least it might help proving my theory);

If in fact, you are accessing the same tenant or if its not related to browser token affinity, then the problem could be something local to your environment (potentially CORS related or SSO/ AD related) which is difficult to diagnose remotely. Please check with your local SSO/ Network admin.

All comments

unknown

Can you please confirm if the Tenant used for testing in Postman and the Tenant that you are accessing via Ming.le are the same?

unknown

Hi Vignesh,

Thanks a lot for the reply. I figured that authenticating messed up my session with ming.le. I verifiy that this is the case when i clear my site data and i able to log into ming.le again.

I was using it to build a google add-on to do bulk upload from google drive into IDM as most of our users are currently running on chrome books. so i just include another step for user to ensure that they logged into ming.le prior to providing access to the application.

unknown

Hi Vignesh,

So I made few more testing based on the examples on the youtube video How to call an ION API in particular OAuth2.0 Authorization Code Grant:

setting token expiration to 15, postman recognise token has expired, it invoke the default browser but it's already recognise that I have logged earlier and prompted the authorisation confirmation rather than a new login request.
note that i didnt logged into mingle before hand. seems like the earlier authorisation created a session in the browser. when i clear the site data of the authorisation page

and invoke the authentication, it prompt back to the intended login page

i can manipulate the migle user time-out value but it doesn't impacted the mingle-sso session.

Is there a way for me to logout this https://mingle-sso.se2.inforcloudsuite.com session created when authorizing or passing login parameter rather than using the authentication page? Hope for your thoughts

Copyright © 2025 Infor. All rights reserved.