Base solution for your next web application
BLACK FRIDAY
From Nov 21
To Dec 1
XXDAYS : XXHRS : XXMIN : XXSEC
SAVE UP TO$3K
Also valid for the
existing customers!
Open Closed

Deploying to Azure - Subdomains - SSL Certificates #10856


0
enrique.mena created

Prerequisites

  • What is your product version? 8.7.0
  • What is your product type (Angular or MVC)? Angular
  • What is product framework type (.net framework or .net core)? .net core

We are trying to deploy to Azure, and we need to deploy to at least two different environments (sandbox and production). Do you have any documentation on a similar use case? What kind SSL Certificate configuration (single certificate, multiple certificates, wildcard, multi-domain, etc.) do we need to get in order to be able to have something like:

SANDBOX Host/API {tenancy-name}-sandbox.api.somedomain.com

Angular {tenancy-name}-sandbox.app.somedomain.com

Public {tenancy-name}-sandbox.somedomain.com

PRODUCTION Host/API {tenancy-name}.api.somedomain.com

Angular {tenancy-name}.app.somedomain.com

Public {tenancy-name}.somedomain.com


3 Answer(s)
  • 0
    ismcagdas created
    Support Team

    Hi,

    For deploying your app to Azure, you can check https://docs.aspnetzero.com/en/aspnet-core-angular/latest/Deployment-Angular-Publish-Azure.

    For the SSL certificate, you can request help from Azure, we don't have much experience about this.

    Thanks,

  • 1
    sedulen created

    @enrique.mena

    Your production environment will work great. Unfortunately what you are trying to achieve is not supported with SSL Certificates for your sandbox environment. Wildcard SSL Certificates do not support the hypenated expression that you are trying. I'm also not certain, but I don't think that DNS resolution will support that hyphenated wildcard expression you are trying to use either.

    You will need a second multi-level subdomain for your "sandbox" environment.

    SANDBOX Host/API {tenancy-name}.api**.sandbox**.somedomain.com

    Angular {tenancy-name}.app**.sandbox**.somedomain.com

    Public {tenancy-name}.sandbox.somedomain.com

    This is how our environments are setup and they work great for us. We host anywhere from 2 to 5 environments of our platform, and for each we have that multi-level subdomain, like *.dev., *.alpha, or *.preview.

    For each environment, we had to setup a wildcard DNS A record and purchase a separate wildcard SSL certificate. I hope this helps.

    -Brian

  • 0
    ismcagdas created
    Support Team

    Thanks @sedulen :)