AP Connector set up issues

bwm561 · 2024-10-02T15:13:28.047Z

Hi all, I’m having loads of trouble setting up the “simple” Bubble App Connector. The documentation Bubble provides is not great.

I want to simply provide a way for users in App A to get to App B and access online courses that they have purchased from App A.

I have things set up according to the documentation. App B is connected to App A. When I log in to App B, it creates the user from App A and authenticates. If I’m already logged in on App A, it simply takes me to App B. So far, so good.

The problem: Nothing else seems to happen. App B seems “stuck” in that it keeps redirecting to its log-in page, and I can’t even navigate around the app. There is no user info displayed anywhere even though the user is created and active in the database. So it appears that I’m logged in; but nothing is happening in App B. When I try to go to a page, it just keeps redirecting me to the App B log-in (even though I’m already logged in via App A).

Any advice?

AliFarahat · 2024-10-02T15:36:35.606Z

I think we need a bit more information at least technically to be able to guide you in the right direction, but did you try to connect to the other app via the API connector either using the workflow endpoint or the data endpoint? Did you create an authentication token that you are passing to those endpoints?

bwm561 · 2024-10-02T16:10:34.145Z

Hi @AliFarahat , yes, I think I set up the connection properly.

In App A (main app), I set up the API and enabled workflow API and data API. For data, I am enabling type User and type Course (to determine which courses the user is enrolled in).
I created an API token for App A.
I enabled 3rd party Oath access for App B
In the App Connector plugin for App B, I set up the info for App A, and inputted the Private key, Client ID, and Client Secret.
I set up the following API calls (screenshot attached) in the App Connector

Screenshot 2024-10-02 at 12.01.13 PM786×275 23.1 KB

In the Workflow for App B, I added the workflow “sign up with a social network” and then added App A as the Oath provider, as indicated in the documentation.

This all seems to be working correctly, so far. When I try to visit App B for the first time while logged in to App A, it creates a user based on App A. However, it doesn’t populate any of the user information from App A, leading App B to think that the user set up is not complete. I think I need more steps?

But how do I create these steps? Do I “make changes to a thing”? However, when I try to do this, it does not seem to be able to draw upon Step 1 (sign up with App A), nor do I seem to be able to link up to the relevant App A data when I try to “get data from an external API”.

This also creates the situation that when I try to navigate around the app, I am sort of “half logged in.” Log in buttons still appear at the top, but technically speaking, a user has been created and is logged in via the Oath.

Thanks!
Bryan

system · 2024-12-11T15:14:18.202Z

This topic was automatically closed after 70 days. New replies are no longer allowed.