Consolidate Access Token Pairing Permission view

Currently when creating an Access Token, this is the flow

1. Hit Create Token CTA
2. Token Details
3. Choose Store Pairing

I can see an instance of why you might want to create a token for another store from this view, but it seems unnecessary and redundant.

I propose removing that Pairing view, and just associating the token to the current store you’re creating it from.

• Removes the additional Pairing view step
• Less bugs or permissions, etc… to potential worry about, and/or test

Open to hearing opposing opinions as well, but wanted to toss this one out there.

[Kukks]

Keep in mind that this page is often linked to from an integration to “pair”, which often does not know about stores and thus needs the store selector up front. But, we can hide it if it was loaded from inside the store obviously

On Fri, Sep 23, 2022, 06:29 d11n @.***> wrote:

@cvchris https://github.com/cvchris yes, go ahead and feel free to reach out to me (on our Mattermost or here) if you have questions!

— Reply to this email directly, view it on GitHub https://github.com/btcpayserver/btcpayserver/issues/4133#issuecomment-1255789603, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAN357X25V43Z5VZMBU54GTV7UW3RANCNFSM6AAAAAAQPWXRRM . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[dennisreimann]

Good point, @kukks. I think something similar like we did in #3880 would work well here too: If there’s no store selected, present the selection as the first step — If the store is present, skip that step and go straight to the pairing.