MITS Discover and Report Single Sign-On feature

1. Generate the URL to the desired piece of MITS content.  These examples are visible on our demo system when logged on as user WILL (password “will”)
2. Grid Report
3. launchFlashScreenAsynchronously.flow takes libraryName and id
4. For example: http://mda.mits.com/mitsdiscover/launchGrid.flow?libraryId=AR.COMPANY.INV&gridId=R.AR.INV
5. Chart report
6. launchChart.flow  takes libraryName and id
7. For example: http://mda.mits.com/mitsdiscover/launchChart.flow?libraryId=WILL&chartId=2041
8. Prompted dashboard:
9. displayFullScreenDashboard.flow  takes libraryName and id and also one parameter for each prompt name, with spaces in the name escaped as %20. The values of these parameters should be the identifier IDs.
10. For example

                                   iii.            http://mda.mits.com/mitsdiscover/displayFullScreenDashboard.flow?libraryName=CUSTOMER.SCORECARDS&id=FS.CUSTOMER.BILL.TO.STATUS.SCORECARD&valuesAreDescriptions=false&Sales%20Rep=1013&Bill%20To%20Customer=103273  

1. This is equivalent to launching the Bill To Customer Status Scorecard with these values:
3. For more example dashboard URLs, inspect the links used any place that MITS Discover offers to let you drill across to a dashboard, like here:
5. The links produced in the product include a “valuesAreDescriptions” parameter which is unused.
6. Dashboards can take a little while to launch, so they can also be launched asynchronously, which displays a loading message while it waits.
7. Instead of just going to the dashboardUri,  go to launchDashboardAsynchronously.flow?dashboardUri=[encoded dashboardUri]
8. For example http://mda.mits.com/mitsdiscover/launchDashboardAsynchronously.flow?dashboardUri=displayFullScreenDashboard.flow%3FlibraryName%3DCUSTOMER.SCORECARDS%26id%3DFS.CUSTOMER.BILL.TO.STATUS.SCORECARD%26Sales%2520Rep%3D1013%26Bill%2520To%2520Customer%3D103273 

                                   iii.            Note that the dashboardUri value has been through a round of percent-encoding

2. Get the authentication token
3. Make a request to  http://[mitsURL]/getToken.md and pass it parameters username and password. 
4. The user name and password can be in the URL, or in GET or POST parameters.
5. For example, http://mda.mits.com/mitsdiscover/getToken.md?username=WILL&password=will
6. This produces an xml response with a token, which will be two integers separated by an underscore, for example
7. <token>14c04fb1088_2</token>
8. Note that it doesn't actually do the authentication at this point
9. Use the token
10. Make another request to http://[mitsURL]/useToken.md?token=[token]
11. The user/pass in the token are authenticated  and now the user is logged in and their session will remain valid until they log out or it times out
12. Now you can make another request to a valid url eg http://mda.mits.com/mitsdiscover/listReports.flow
13. Optionally, you can combine those steps  by using the redirectUrl parameter. The passed URL should be encoded, which might mean another layer of encoding.  For example, having gotten the token for user WILL as above,  (you’ll need to replace the token with a new one to see it work)
14. http://mda.mits.com/mitsdiscover/useToken.md?token=1554aeae370_2&redirectUrl=displayFullScreenDashboard.flow%3FlibraryName%3DCUSTOMER.SCORECARDS%26id%3DFS.CUSTOMER.BILL.TO.STATUS.SCORECARD%26Sales%2520Rep%3D1013%26Bill%2520To%2520Customer%3D103273 
15. After using useToken.md once, the token is invalidated because it is no longer needed.  The user is now logged in and can move about, or subsequent links directly to content can be made without the useToken option.
16. Troubleshooting
17. If the token has timed out or been removed because it was used, you’ll see an error about “No Token Provided”
18. If the user is already logged in and you hit getToken.md a second time you get PRE_AUTHENTICATED for a token.  Hit logoutRedirect.flow to clear the current user out of the session, eg   http://mda.mits.com/mitsdiscover/logoutRedirect.flow
19. Configuration
20. The token’s timeout period (maximum time between when it is requested and when it is used) can be set in MITSDiscover.servlet.authCookieTimeout in the mitsdiscover.properties file 
21. Regular session timeout can be configured with  MITSDiscover.session.timeoutMinutes