AADSTS90102 - 'redirect_uri' value must be a valid absolute Uri.

%3CLINGO-SUB%20id%3D%22lingo-sub-896650%22%20slang%3D%22en-US%22%3EAADSTS90102%20-%20'redirect_uri'%20value%20must%20be%20a%20valid%20absolute%20Uri.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-896650%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20getting%20this%20error%20message%20when%20Users%20load%20our%20Sharepoint%20based%20Intranet%20site%20which%20contains%20a%20Yammer%20Feed%20webpart.%20The%20Users%20experiencing%20this%20issue%20are%20all%20members%20of%20a%20group%20to%20which%20someone%20posted%20a%20Stream%20video.%26nbsp%3BThe%20URL%20for%20the%20page%20contains%20%22%3CSTRONG%3Eclient_id%3Dcf53fce8-def6-4aeb-8d30-b158e7b1cf83%26amp%3Bredirect_uri%3Dundefined%3C%2FSTRONG%3E%22%26nbsp%3B%20The%20id%20cf53fce8-def6-4aeb-8d30-b158e7b1cf83%20in%20Azure%20shows%20the%20source%20of%20this%20issue%20as%20being%20%22Microsoft%20Stream%20Portal%22.%26nbsp%3B%20Can%20anyone%20tell%20me%20where%20redirect_uri%20is%20defined%20and%20what%20it%20should%20be%20set%20to%26nbsp%3Bto%20avoid%20this%20issue%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-971745%22%20slang%3D%22en-US%22%3ERe%3A%20AADSTS90102%20-%20'redirect_uri'%20value%20must%20be%20a%20valid%20absolute%20Uri.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-971745%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F78711%22%20target%3D%22_blank%22%3E%40Jack%20Pottinger%3C%2FA%3E%26nbsp%3BI%20am%20getting%20this%20same%20error%20when%20adding%20a%20Stream%20embed%20on%20a%20SharePoint%202013%20page.%26nbsp%3B%20This%20error%20only%20shows%20in%20IE%2011%20and%20not%20in%20Chrome.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1045921%22%20slang%3D%22en-US%22%3ERe%3A%20AADSTS90102%20-%20'redirect_uri'%20value%20must%20be%20a%20valid%20absolute%20Uri.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1045921%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F87014%22%20target%3D%22_blank%22%3E%40Chris%20Schuh%3C%2FA%3E%26nbsp%3BWe%20found%20the%20source%20of%20our%20issue%20was%20Our%20sharepoint%20site%20was%20setting%20document%20mode%20to%20IE10%20for%20compatibility%20reasons.%26nbsp%3B%20We%20couldn't%20change%20this%20because%20that%20would%20have%20broken%20other%20functionality%20with%20the%20site.%26nbsp%3B%20Shortly%20afterwards%20the%20Error%20message%20was%20made%20%22less%20prominent%22.%26nbsp%3B%20So%20the%20individual%20videos%20in%20embeded%20yammer%20feed%20still%20aren't%20able%20to%20play%20but%20at%20least%20the%20rest%20of%20the%20site%20loads.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

We are getting this error message when Users load our Sharepoint based Intranet site which contains a Yammer Feed webpart. The Users experiencing this issue are all members of a group to which someone posted a Stream video. The URL for the page contains "client_id=cf53fce8-def6-4aeb-8d30-b158e7b1cf83&redirect_uri=undefined"  The id cf53fce8-def6-4aeb-8d30-b158e7b1cf83 in Azure shows the source of this issue as being "Microsoft Stream Portal".  Can anyone tell me where redirect_uri is defined and what it should be set to to avoid this issue?

5 Replies

@Jack Pottinger I am getting this same error when adding a Stream embed on a SharePoint 2013 page.  This error only shows in IE 11 and not in Chrome.

@Chris Schuh We found the source of our issue was Our sharepoint site was setting document mode to IE10 for compatibility reasons.  We couldn't change this because that would have broken other functionality with the site.  Shortly afterwards the Error message was made "less prominent".  So the individual videos in embeded yammer feed still aren't able to play but at least the rest of the site loads.

@Jack Pottinger  - Can you try again on IE11 with the IE10 document mode set? We made some changes reccently in the last several weeks to work around this and allow Stream embed to still work on IE10 document mode. I'm hoping this is working for you now.

@Marc Mroz Yes this issue stopped occurring / became less prominent around this time. I think instead of the error taking up the entire page it became limited to the embedded component of the page.