search

salesforceidentity / aloha-applauncher

Apex / Visualforce for a Custom App Launcher, based on the Salesforce IT Deployment
Other
3 stars 1 forks source link

App Launcher from unauthorized user #1

Open RupertBarrow opened 5 years ago

RupertBarrow commented 5 years ago

Hi Chris, I would like to use App Launcher everywhere in my universe :

The idea is to centralize all app menu management in one place, use Salesforce Identity and SSO for connected apps.

My question : can I query for AppMenuItems (via API) from a non-authorized/guest user ?

@cmortimore

cmortimore commented 5 years ago

What's the use-case? Generally speaking the App Launcher is shown in authenticated scenarios and only shows the items the user has access to.

RupertBarrow commented 5 years ago

Our client has Salesforce (internal) + Customer Community + multiple websites/webapps, some of which support authenticated users, and others are either totally public or part public and part authenticated.

They are very Salesforce-centric, and are moving many of their webapps onto their Customer Community, either totally "hosted" or just for Salesforce Identity authentication.

They have gone through a serious process of identifying the personas of their community at large, and are setting up perm sets, custom authorizations and connected apps to pull all this together.

Now my point : on a website/webapp half public, half authenticated, they would like to have a seemless experience for visitors/users using the same hamburger menu/app launcher. In the first case (public visitor), it would list all websites/webapps they have added to the App Launcher as connected apps. In the second case (authenticated), it would also add services or apps (also added to App Launcher as Salesforce apps) available only for authenticated users.

It would be nice to be able to : 1) put the list of all these websites and apps into one place : identify them as connected apps and add them to the App Launcher 2) assign these apps to profiles (personas) : for authenticated user profiles, but also for Guest profiles of Salesforce Communities 3) in Salesforce Communities, we would use the standard App Launcher menu (or custom app ;) and standard Salesforce Community login experience 4) on websites hosted off of Communities, we would use a custom Lightning Out web component to list available apps (AppMenuItem looked up via API) of the public visitor or authenticated user, and use Embedded Login to let visitors authenticate (and even self-register)

What do you think ?

Le 14 oct. 2019 à 18:17, cmortimore notifications@github.com a écrit :

What's the use-case? Generally speaking the App Launcher is shown in authenticated scenarios and only shows the items the user has access to.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/salesforceidentity/aloha-applauncher/issues/1?email_source=notifications&email_token=ALTAP54WVPKDCGRVQTLITJTQOSLS5A5CNFSM4JAQRZKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBFNIHI#issuecomment-541774877, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALTAP5ZQAZ6JK57A2Z34BWDQOSLS5ANCNFSM4JAQRZKA.

cmortimore commented 5 years ago

At that point it's just a list of links. The difficult part will be there is no way to specify which ones are available anonymously.