{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
originally posted in:BungieNetPlatform
4/25/2017 3:35:12 PM
3
I just noticed in the Bungie.net Authentication post, it mentions this:
[quote]Using a web view is strongly discouraged by Bungie. We will block it using technical means where possible. In the very least, applications that implement the sign in flow via a web view will not be featured or promoted on Bungie.net in any way. We may take other measures as well.[/quote]
I'm curious if it is possible that the redirection mechanism used by either Xbox live/bungie.net is not compatible with the web view used in the Alexa companion app. Any help or advice with this problem would be greatly appreciated.
English
-
Did you solve this problem ?
-
The problem resolved itself after one of the last updates to the Alexa companion app. It started using a real safari web view controller and that seemed to fix the redirection issues I was having.
-
Do you think you could help me get my Alexa Skill connected to Bungie.net? I created my API key through Bungie's application portal, and got the OAuth Authorization URL and client ID from there, and set the redirect URL in there that Alexa Skills Kit configuration gave me in there. I've made several alexa skill apps before, but never did the account linking. When I install my Alexa Skill it pops up the Bungie.net authorization for my account and asks me to approve (that looked very promising), but when I click "Approve" Amazon gives me a screen that says it failed, and I don't seem to have any means of troubleshooting it. Some things I'm unsure of are: 1) At this point, when the skill is getting authorization to Bungie, does my code for my skill have anything to do with it? I didn't update the code for this yet, I'm thinking the account linking is all before it touches my code and ultimately I'll just use the resulting auth token in my code, but everything else on getting the token is handled by amazon and bungie. 2) I'm unclear on the Authorization Grant Type section. I know I need "Auth Code Grant" selected for refreshing tokens, and I plugged in the Access Token URI from bungie's documentation "https://www.bungie.net/Platform/App/GetAccessTokensFromCode/" but I don't know what the "Client Secret" and "Client Authentication Scheme" should be set to. Looks like other non-Bungie Oauth connections have a client secret in addition to the client id. However, the Bungie Application Portal only gives me a client id and no client secret. I tried plugging my api key into the client secret in amazon's configuration, but obviously that didn't work. I'm guessing this is where it's going wrong. Amazon is asking for a client secret and Bungie hasn't provided me one and I don't know where to get it.
