Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

System Profile

System Full Name

Aeronautical Products API

System Full Name (FR)

Produits Aeronautique - Prestation de services API

Subject Matter Expert

Michelle Coelho

Source Code Location

https://dev.azure.com/transport-canada/DSD-CIVAV Support/_git/NAPA-SNAPA_API

Client ID

https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationMenuBlade/Overview/appId/22897920-2e0b-4e97-80ca-fbc41c5805cb/isMSAApp/

KeyVault Secret

https://portal.azure.com/#@034gc.onmicrosoft.com/asset/Microsoft_Azure_KeyVault/Secret/https://civav-dev-keyvault.vault.azure.net/secrets/APSD-PAPS-PowerApps

Technology Assessment

Platform Type

 

Database Platform and Version

Oracle 11g 

Development Language and Framework

C#, .NET Core 6

Operating System and Version

 

Additional Dependencies

 

Authentication

 Azure AD

Environment Access Information

ENV

UNC

WWWFILES

URL

DB

Dev

 

 

https://catcappsx.tc.gc.ca/Saf-Sec-Sur/2/NAPA-SNAPA_API/swagger/index.html

NNACEP.WORLD

Acc

 

 

https://wwwappstestext.tc.gc.ca/Saf-Sec-Sur/2/NAPA-SNAPA_API/swagger/index.html

NNACEP.WORLD

Note: the server dev don’t have a certificate to work with https.

API Architecture

API Infrastructure

➕ points

➖ points

Integration with Azure (Azure AD and possibility with KeyVault)

VPN dependency

Using the last version for software development platform

Oracle connection dependency

Not scalable because is inside IIS

30% of the app's power is being used

Availability not guaranteed 24/7

The goal

This same API, one time in the cloud, all negative points will be removed automatically.

Azure configuration

App registration

 Civil Aviation - Aviation civile

Database Platform and Version

Oracle 11g 

Development Language and Framework

C#, .NET Core 6

  1. The redirect URL from the API needs to be registered on app registration

  2. The option Access tokens need to be activated

  3. In Exposed API, add a scope

  4. Give access to your client ID

  5. In API permissions, grant access to your scope

  6. This configuration will be used in your API

  7. To configure your endpoint, you can see from here

API Access

  1. Open the API in development (see the address up)

  2. Click on Authorize

  3. Select the scope and click on Authorize again. The Microsoft login page will open and you need to enter your credentials as MSTeams.

  4. After that, you can try to execute an API

  • No labels