The Curity Identity Server should now be deployed on the platform of your choice, an authenticator and client should have been configured, and you have probably tested out the deployment using for example OAuth.tools, the OAuth Assistant or cURL. If not, let’s review the getting started articles that will get you there and some recommended next steps to look at after that.
There are several options to deploy the Curity Identity Server. The getting started track outlines the more common scenarios.
Both of the above could also benefit from leveraging ngrok in order to expose the Curity installation publicly, how to achieve that is outlined in the Exposing Curity Using ngrok article.
Getting the Curity Identity Server up and running on the most common cloud platforms is fast and easy.
- Install using Helm chart. This applies to any platform that can run a Kubernetes cluster.
- AWS with a CloudFormation template or the fast and easy AWS AMI
- Azure using an ARM template
- Install on Google Cloud Platform
Helm chartThe Helm chart can be used to easily deploy on AWS, Azure and GCP.
The minimum needed in order to get a useful deployment of the Curity Identity Server running is to run through the basic setup wizard, configure an Authenticator and a Client. All are outlined in these articles. Check the Suggested next steps section for additional reading on this topic.
With the deployment and configurations done it’s time to test what’s been set up so far. There are several ways to do this, and these articles provide some good options but are not the only ways to test.
At this point, a basic deployment should be up and running and tested. Here are some suggested next steps that would detail some more advanced configurations and integrations.
- Using the Curity CLI
- Clustering using the Helm chart
- Using the Login API demo client
- Account linking with Facebook
- Templatized and non templatized DCR
- The split token pattern
- The phantom token approach
- Integrating with Apigee using phantom token or with the split token pattern
- Integrating with the AWS API Gateway
- Integrating with Cloudflare
- Integrating with the Kong API Gateway
- Integrating with Microsoft Azure API Management
- Using Curity as an IDP for Salesforce
- Integrating with Azure AD
- Authenticating to MuleSoft Anypoint using Curity
- Protect access to applications running in Jetty using Curity
- Use the mod_auth_openidc module with Curity
- Log to Datadog
- Log to Splunk
- Send Curity alarms to PagerDuty
In addition to these articles on various topics Curity provides lots of open sourced and sample code of various integrations and plugins. Check out some of the code examples.
Let’s Stay in Touch!
Get the latest on identity management, API Security and authentication straight to your inbox.