Application Authenticity Protection in Native Windows Universal applications
This is a continuation of the Application Authenticity Protection tutorial.
The application-descriptor.xml file
Modify the application-descriptor.xml file on your application by adding a security test configured for application authentication.
Adding the security test
securityTest attribute to the Windows / Windows Phone environment element. For example:
Adding the package family name
packageName attribute to the Windows / Windows Phone environment element. For example:
The package name can be extracted from Visual Studio. Open the Project in Visual Studio and search for
Package.appxmanifest file. Navigate to the Packaging Tab and pick up the package name as shown below.
Adding the runtime package to enable application authenticity
- Open your Native Mobile First Project in Visual Studio. Choose the environment, either Windows or WindowsPhone in your solution. Choose References in the environment and select to Add Reference.
- In the Reference Manager Window, select Windows 8.1 -> Extensions, as shown. This will list out the SDKs applicable to your project.
- Add the
Microsoft Visual C++ 2013 Runtime Package for Windowsor the
Microsoft Visual C++ 2013 Runtime Package for Windows Phonebased on which environment your are adding it to.
- Now build your project to generate the final executable (.appx) and pass it to the
wladmcommand to enable extended application authenticity as explained earlier
Inclusive terminology note: The Mobile First Platform team is making changes to support the IBM® initiative to replace racially biased and other discriminatory language in our code and content with more inclusive language. While IBM values the use of inclusive language, terms that are outside of IBM's direct influence are sometimes required for the sake of maintaining user understanding. As other industry leaders join IBM in embracing the use of inclusive language, IBM will continue to update the documentation to reflect those changes.