userdata
2 TopicsMSIX AppAttach FSLogix Profile issue between packaged app versions
Has anyone experienced the following scenario: Application (PowerBI) packaged as MSIX and delivered via App Attach: Package Name: PowerBI-2.104.702.0.MSIX Delivered via App Attach to AVD FSLogix Profile created, and Application user data stored path: \\CLIENTNAME.file.core.windows.net\fslogix\$GUID_username%\Profile_User_name.vhdx\ Profile\AppData\Local\Packages\PowerBI-2.104.702.0\LocalCache\Local\Microsoft\Power BI Desktop (or similar) End user can access application, app profile data is retained to FSLogix and works as expected between sessions, retaining app settings etc. Now, a new version is required: Package Name: PowerBI-2.104.941.0.MSIX Delivered via App Attach to AVD FSLogix Profile created, and Application user data stored path: \\CLIENTNAME.file.core.windows.net\fslogix\$GUID_username%\Profile_User_name.vhdx\ Profile\AppData\Local\Packages\PowerBI-2.104.941.0\LocalCache\Local\Microsoft\Power BI Desktop (or similar) So, between the different versions of the same Application, I am not able to access the roaming profile application data from the original package, forcing my users to have to re-configure the application afresh for the new release. I could just repackage the new version using the EXACT SAME name, but this makes it impossible to differentiate between packages, and also does not meet any version control naming conventions. Has anyone come across this before, and has anyone discovered a viable solution? Thanks NickSolved2.2KViews0likes2CommentsAccess session (UniversalBot.loadSession) and it's userData from tab
Hello! Is there any possibility to access the current session (UniversalBot.loadSession with an address object) and the associated userData when handling a request for a tab? There is microsoftTeams.getContent on the tab client side, but that information is insecure and cannot be used for authentication as stated in the docs. When handling a bot request, e.g. handling a messaging extension request for a search which needs authentication to an external IDP, this information can be accessed through the address object from the event object in an onQuery-handler, but so far I could not figure out how to do this when handling a request for a tab. Especially I don't know how to access the address object with which the session can be loaded. I would need this to use one single authentication flow with the bot but not an additional tab based authentication flow. I want to avoid using microsoftTeams.authentication.authenticate as a second parallel authentication flow to the bot authentication initiated with responding with composeExtension/type "auth"/"openUrl". Using two parallel authentication flows may confuse the user as e.g. when the user first uses the tab flow the bot/messaging extension needs an additional authentication, and when using the bot flow first the tab can be authenticated through localStorage (writing the access token into the localStore in the authentication callback site) on the machine where the authentication took place, but when signed in to Teams simultaneously on another machine, the bot can use the access token there too, as the Teams sessions is the same, but the tab is not authenticated as it cannot access the session. Regards, Dominik1.6KViews0likes4Comments