Setup Easy Sample App Security
TheAppsPajamas NuGet depends on two JSON files, both of which are placed at the root of your project by the NuGet package.
tapsettings.json
{
"TapAppId" : "your-tap-app-id-here"
}
This file is for the project configuration and has the Tap App Id. We recommend saving this project in git
tapsecurity.json
{
"UserName" : "your-user-name",
"Password" : "your-password",
"ServiceUserAccessKey": "service-user-access-key-preferred-option"
}
We recommend that you git ignore the TapSecurity.config file.
We also recommend creating a Team, and a Service User Access Key, rather than using your User Name and Password to build your Tap App - see our documentation on Teams for examples of how to setup a team.
In a continuous integration setup the security information for a Service User Access Key should be stored with the CI provider - see our documentation on Continuous Integration Pipelines for example of how to set this up.
If you try to build your project without completing the information in these files, you'll get a build error.
First put your Tap App Id in the tapsettings.json file. You can see the Tap App Id in the top right corner on the dashboard beside the key icon.
tapsettings.json
{
"TapAppId" : "4x6sshgyv4cqe3zq84fd6g0pdk"
}
tapsecurity.json
{
"UserName" : null,
"Password" : null,
"ServiceUserAccessKey": "your-access-key-here"
}
In a Cross platform solution with multiple projects you can move the tapsettings.json and tapsecurity.json files to the root of your solution and the NuGet package will tree walk up the directory structure and use the settings files at the highest folder in the tree