Help with LimitedAccessFeatures::TryUnlockFeature in a unpackaged application

[jso-mega]

Hello!
I haven't found any documentation about how to use LimitedAccessFeatures::TryUnlockFeature in a non-packaged app, i have managed to make it work in a test packaged app.

I understand this should be posible because the LAF Access Token Request Form allows you to specify that the app is not packaged.

Any advise?

Thanks.

[jso-mega]

Maybe @riverar can help me?

[jso-mega]

Hello Rafael, thanks for your answer. I'll explain a little more detailed :

So in a packaged app we have the "Package Family" attribute, for example : Fabrikam.Fabrikam_zpdnekdrzrea0, we can take the last part of this string zpdnekdrzrea0 as a publisher id and add it to the front of the attestation: zpdnekdrzrea0, for example zpdnekdrzrea0 has registered their use of... as you suggested in https://withinrafael.com/2021/01/04/generating-valid-tokens-to-access-limited-access-features-in-windows-10/

My issue/concern is: i'm not in a packaged app, so i don't have Package Family i can't get the publisher id, how i can create and attestation that need the publisher id? in a non-packaged app i provided to microsoft the Application Name and the Publisher Name.

Thanks for your time.

[riverar]

Ah, I understand now.

To clarify: An app can be packaged or unpackaged. Unpackaged apps can have identity or not have identity.

I believe all of the Limited Access Features currently require your app to have identity. To get an identity for your unpackaged app, you will need to set up a package with external location (docs). It's a bit convoluted but all the steps are there and should work. After completing those steps, you will have a PackageFamily value to use in the LAF token.

I'll need to do some further research to see if it's possible to skip this step.

[jso-mega]

Thanks for your answer, i'll review the docs. Looking forward your research comments.

[jso-mega]

So at last i've managed to make this work, in a unpackaged application i added/embeded a .rc file with the following:
Identity LimitedAccessFeature { L"AppName_testidpublisher123" }
then using the name "AppName_testidpublisher123" as a PackageFamilyName in the https://withinrafael.com/api/windows_laf_token i get the token to be used in LimitedAccessFeatures.TryUnlockFeature("com.microsoft.windows.taskbar.pin", tokenFromWebApi, attestation)
The last argument is the attestation formed in the following way:

var publishedId = testidpublisher123
var featureId = com.microsoft.windows.taskbar.pin

attestation = $publisherId has registered their use of $featureId with Microsoft and agrees to the terms of use.

[ghost1372]

A sample app which is documented can be useful

[hzq4git]

I wrote a demo C++ Windows Desktop Application using VS 2019, succeeded to TryUnlockFeature according to the method you said. The property named TaskbarManager.IsSupported is true, but TaskbarManager.IsPinningAllowed Property is false. Don't know how to investigate further to pin the demo application to taskbar.

[jso-mega]

It happened the same to me, IsPinningAllowed only return true if i'm not in debug mode and the call is performed when the application is visible to the user (no a console app) i created an app with a dialog and a button to test it. The app can't even be minimized in case you try to pin using some kind of timer..