ASP.NET Core sample app illustrating how to make use of the Steeltoe CloudFoundry External Security Provider for Authentication and Authorization against a CloudFoundry OAuth2 security service (e.g. UAA Server or Pivotal Single Signon Service).
NOTE: For simplicity, we've moved the instructions for utilizing the SSO Tile with this sample
- Cloud Foundry instance
- Windows support on Cloud Foundry (OPTIONAL)
- .NET Core SDK installed
- CloudFoundry UAA Command Line Client installed
This sample requires an OAuth2 service in your org/space. These instructions will use the UAA Server as the OAuth2 service.
Before creating the OAuth2 service instance, we need to use the UAA command line tool to establish some security credentials for our sample app. Target your UAA server:
- uaac target uaa.
YOUR-CLOUDFOUNDRY-SYSTEM-DOMAIN(e.g.uaac target uaa.system.testcloud.com)
Next, authenticate and obtain an access token for the admin client from the UAA server so that we can add our new application/user credentials. You will need the Admin Client Secret for your installation of CloudFoundry for this step. If you are using Pivotal CloudFoundry (PCF), you can obtain the secret from the Ops Manager/Elastic Runtime credentials page under the UAA section. Look for Admin Client Credentials and then use it as follows:
- uaac token client get admin -s
ADMIN_CLIENT_SECRET
Note: To see the token that was retrieved, run the command
uaac contexts
After authenticating, add a new user and group to the UAA Server database. Do NOT change the group name: testgroup as it is used for policy based authorization in the sample application. Feel free to change the username and password to anything you would like.
- uaac group add testgroup
- uaac user add dave --given_name Dave --family_name Tillman --emails dave@testcloud.com --password Password1!
- uaac member add testgroup dave
After adding the user and group, we are ready to add our application as a new client to the UAA server. This step will establish our application's credentials and allow it to interact with the UAA server. Use the line below once you have replaced the YOUR-CLOUDFOUNDRY-APP-DOMAIN with the domain used by your cloud foundry instance.
uaac client add myTestApp --scope cloud_controller.read,cloud_controller_service_permissions.read,openid,testgroup --authorized_grant_types authorization_code,refresh_token --authorities uaa.resource --redirect_uri http://single-signon.`YOUR-CLOUDFOUNDRY-APP-DOMAIN`/signin-cloudfoundry --autoapprove cloud_controller.read,cloud_controller_service_permissions.read,openid,testgroup --secret myTestAppLast, we will create a user-provide service that includes the appropriate UAA server configuration data. Use the sample below to pass the parameters directly to the cf cups command, replacing <YOUR-CLOUDFOUNDRY-SYSTEM-DOMAIN> with your domain.
cf target -o myorg -s development
cf cups myOAuthService -p "{\"client_id\": \"myTestApp\",\"client_secret\": \"myTestApp\",\"uri\": \"uaa://login.<YOUR-CLOUDFOUNDRY-SYSTEM-DOMAIN>\"}"- cf target -o myorg -s development
- cd samples/Security/src/CloudFoundrySingleSignon
- dotnet restore --configfile nuget.config
- Publish app to a directory selecting the framework and runtime you want to run on.
dotnet publish -f netcoreapp3.1 -r linux-x64dotnet publish -f netcoreapp3.1 -r win10-x64
- Push the app using the appropriate manifest.
cf push -f manifest.yml -p bin/Debug/netcoreapp3.1/linux-x64/publishcf push -f manifest-windows.yml -p bin/Debug/netcoreapp3.1/win10-x64/publish
Note: The provided manifest(s) will create an app named
single-signonand attempt to bind it to the user-provided servicemyOAuthService.
After pushing the app, you should see something like the following in the logs:
2016-08-05T07:23:02.15-0600 [CELL/0] OUT Creating container
2016-08-05T07:23:03.81-0600 [CELL/0] OUT Successfully created container
2016-08-05T07:23:09.07-0600 [APP/0] OUT Running .\CloudFoundrySingleSignon
2016-08-05T07:23:14.68-0600 [APP/0] OUT Hosting environment: development
2016-08-05T07:23:14.68-0600 [APP/0] OUT Content root path: C:\containerizer\75E10B9301D2D9B4A8\user\app
2016-08-05T07:23:14.68-0600 [APP/0] OUT Application started. Press Ctrl+C to shut down.
2016-08-05T07:23:14.68-0600 [APP/0] OUT Now listening on: http://*:51217At this point the app is up and running. You can access it at http://single-signon.`YOUR-CLOUDFOUNDRY-APP-DOMAIN`/.
Note: To see the logs as the app runs, execute this command:
cf logs single-signon
On the app's menu, click on the Log in menu item and you should be redirected to the CloudFoundry login page. Enter dave and Password1!, or whatever name/password you used above, and you should be authenticated and redirected back to the single-signon home page.
Two of the endpoints in the HomeController have Authorization policies applied:
[Authorize(Policy = "testgroup")]
public IActionResult About()
{
ViewData["Message"] = "Your application description page.";
return View();
}
[Authorize(Policy = "testgroup1")]
public IActionResult Contact()
{
ViewData["Message"] = "Your contact page.";
return View();
}If you try and access the About menu item you should see the About page as user dave is a member of that group and is authorized to access the end point.
If you try and access the Contact menu item you should see Access Denied, Insufficent permissions as dave is not a member of the testgroup1 and therefore can not access the end point.
If you access the InvokeJwtSample menu item, you will find the app will attempt to invoke a secured endpoint in a second Security sample app CloudFoundryJwtAuthentication. In order for this to be functional you must first push the CloudFoundryJwtAuthentication sample using the Readme instructions.
Once you have CloudFoundryJwtAuthentication up and running, then if you access the InvokeJwtSample menu item when you are logged in, you should see some values returned from the CloudFoundryJwtAuthentication app. If you are logged out, then you will see a 401 (Unauthorized) message.