#apeindex

1 messages · Page 1 of 1 (latest)

jolly flameBOT
teal marlin
light thunder
#

Hello! Can you tell me a bit more about what you're trying to do and what's stopping you?

teal marlin
#

TL;DR - stripe apps upload doesn't work if you just have a manifest and don't have UI components

#

To be a little more specific about what I would like to do: I would like to make a bare manifest so that I can get an OAuth app set up in the Stripe UI, so that I can get the secret and start implementing the flows as documented here: https://stripe.com/docs/stripe-apps/install-links-oauth

light thunder
teal marlin
#

I'm not sure I follow; authentication to what?

#

I'm looking to implement a normal backend-only OAuth2 client app flow - they don't typically require creating UI components in the OAuth provider service 🙂

light thunder
#

The OAuth authentication process, so the user can give your app access to their account.

teal marlin
light thunder
teal marlin
#

Thank you for your help, but I'm still confused - that looks like Stripe is the OAuth client and I'd be the provider

#

I'm looking for the other way around; Stripe's the OAuth provider

light thunder
#

I honestly don't know much about that beta. You should probably wait for an answer on the GitHub issue, or write in to Stripe Support for help with beta features: https://support.stripe.com/contact/email

teal marlin
#

Sounds good - I will do that, but if it's OK I'd like to nudge gently here, I don't think I've correctly articulated what I am trying to do such that we're understanding it the same way yet

light thunder
#

Sure.

teal marlin
#

I think this has been a feature that Stripe has supported for a very long time, back through the Connect times and everything

#

This is super common on the internet; I am looking to import some data on my customers' behalf by letting them authorize an App we control to access their account

#

This would be fine, but step 1 is always "create the oauth app in the provider site, and get the client key and client secret", which seems impossible to do currently, even though Stripe is documented as supporting pure backend-only apps

#

There's no UI component that makes sense here; so I am hoping you can offer a way to provision an App which doesn't include a UI

#

So I think the question is, how do I provision an OAuth App in Stripe, if stripe apps upload doesn't work without UI components?

light thunder
teal marlin
#

Yes, that's correct.

#

From reading the documentation, it seems like Stripe intends this to still be possible, but just via Apps

light thunder
#

It is, yep, and we have a migration guide linked from that page, but as far as I know a UI component is required.

teal marlin
#

Will Stripe approve Apps which just contain a blank UI?

#

(the problem I'm looking to articulate is that there's just no UI component that makes sense here as far as I can tell)

#

I could provide links to how other sites such as Google etc implement their OAuth Apps if that would clarify anything.

light thunder
#

Typically a Stripe App would, at minimum, have a UI indicating what the app is doing, where it came from, kinda like an "about" page.

teal marlin
#

Ah, on other platforms those are config values in the OAuth App profile, typically called a Consent screen

#

I'll file a ticket, it also might be worth checking on this internally to make sure that it's the intent that backend-only apps must build their own consent screens / app profiles.

light thunder
#

I checked internally and found others talking about this, and it sounds like a UI is required, but I'm asking the Stripe Apps team as well. Not sure when they'll be available to respond though, so a ticket is your best bet for a guaranteed response.

teal marlin
#

Thank you!

#

I'm going to step away, have a great evening and thanks for your time.