Popup integration question
Hi everyone, When creating an new box application there is an option to create a new web application integration, which seems to come it two flavors - a popup or a server-side integration.
- Your integration will open a popup
- Your integration will run server-side only
Right now I am focused on the popup integration but am stuggling though figuring out what url, query string, and callback parameters I should put into the client callback url input. This is the input just below the preliminary callback URL input which is optional.
Whatever I put in there results in a blank white popup (but not after some successful back and forth communication). I am expecting to see (trying to get) a popup similar to the Salesforce integration I see when I click More Actions. The Salesforce integration was pre-loaded in my account along with a Google integration.
Here are the details.
When I put in this url:
http://54.214.96.153/box/popup.php
With these callback parameters:
- #file_id#
- #auth_code#
- #redirect_to_box_url#
I do get some communication to my popup.php file. It does capture communicaiton being sent from the BOX server, which seems to be what the documentation says would happen.
Specifically I get this:
{"file_id":"blabla123","code":"F5ncSRwwQrhVtQFaM3NviVoUmedt","redirect_to_box_url":"https:\/\/app.box.com\/index.php?rm=box_openbox_redirect_to_box&service_action_id=8422&item_id=blafsdfdsblabla&item_type=file&auth_token="}
It's also not clear to me what should my popup.php file should return?
I've tried taking the auth_code and POSTing it back to get an access_token which I successfully do, but the UI element within BOX (my integration) consistanty results in blank white screen. I've tried also returning HTML (which is my goal) and I still get a blank white screen.
If anyone can provide feedback on what client callback url should look like and what my service should return so I can display an HTML popup that would be much appreacted.
-Doug
サインインしてコメントを残してください。
コメント
0件のコメント