CODEWITHSUNDEEP
azuresingle-sign-onoffice365azure-active-directorywindows-store
n1941
n1941

Reputation: 41

We were unable to launch your app from the 'My Apps' launcher

After submitting app to windows store, our app is rejected with the following message.

"We were unable to launch your app from the 'My Apps' launcher. When we launch your app from the My Apps launcher, during an authenticated O365 session, we are prompted to re-authenticate to your app."

What we did is, once the user logs into our app with o365 credentials, our app gets added to user's O365 my apps dashboard. When the user clicks on, our app in O365 launcher it launches the login page of our app instead of automatic login.

Step-by-step:

  1. User visits our web page "http://portal.myedutor.com/users/sign_in"
  2. User clicks on "Login with Microsoft credentials"
  3. User signs in using O365 account
  4. Now user has an active session with our application
  5. User visits "http://portal.office.com" and signs in using same credentials
  6. Within a couple of minutes user sees the "IGNITOR" app in "O365 My Apps dashboard"
  7. Clicking on the app user is taken to the homepage of our application

Now the problem we are facing is, once the user clicks on our app in step-7 he is again asked to login, we are not able to send any session information on app click. We are using open ID protocol for SSO.

Kindly guide us how to maintain session in such scenario. Thanks a lot in advance.

Upvotes: 3

Views: 1026

Answers (1)

Jackie
Jackie

Reputation: 2030

One thing that might be missed here is when you register your app with Active Directory, you used the main login page for SIGN-ON URL, aka, http://portal.myedutor.com/users/sign_in.

However, in order to directly redirect you to the Office 365 login page, you should use Office 365 redirect URL in this case.

For example, when I was testing it locally, I make sure I used localhost:xxxx/account/singin for my SIGN-ON URL, like below,

enter image description here

Upvotes: 1

Related Questions