Version 0.5.0

CHANGELOG.md

@@ -5,6 +5,14 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html)
 
+## [0.5.0] - 2025-03-12
+
+### Changed
+
+- Changed possible Instance values to DEV, TST, ACC, PRD ([#35](https://github.com/EUCTechTopics/PSIdentityNow/pull/35))
+
+[0.5.0]: https://github.com/EUCTechTopics/PSIdentityNow/releases/tag/v0.5.0
+
 ## [0.4.0] - 2025-02-27
 
 ### Changed

PSIdentityNow/PSIdentityNow.psd1

@@ -12,7 +12,7 @@
     RootModule = 'PSIdentityNow.psm1'
 
     # Version number of this module.
-    ModuleVersion = '0.4.0'
+    ModuleVersion = '0.5.0'
 
     # Supported PSEditions
     CompatiblePSEditions = 'Core'

readme.md

@@ -55,6 +55,12 @@ To use the SDK with your IdentityNow tenant, you must configure authentication b
    Alternatively, you can use instance specific environment variables. If these variables are set, you have to specify the `-Instance` parameter when running `Connect-IDNW`:
 
    ```powershell
+   $env:IDNW_DEV_BASE_URL=https://[tenant]-dev.api.identitynow.com
+   $env:IDNW_DEV_CLIENT_ID=[clientID]
+   $env:IDNW_DEV_CLIENT_SECRET=[clientSecret]
+   $env:IDNW_TST_BASE_URL=https://[tenant]-tst.api.identitynow.com
+   $env:IDNW_TST_CLIENT_ID=[clientID]
+   $env:IDNW_TST_CLIENT_SECRET=[clientSecret]
    $env:IDNW_ACC_BASE_URL=https://[tenant]-sb.api.identitynow.com
    $env:IDNW_ACC_CLIENT_ID=[clientID]
    $env:IDNW_ACC_CLIENT_SECRET=[clientSecret]
@@ -65,13 +71,19 @@ To use the SDK with your IdentityNow tenant, you must configure authentication b
 
 2. **Connect to IdentityNow**
 
-   Use the `Connect-IDNW` command to authenticate using secrets from the registered Key Vault. Specify the `-Instance` parameter (e.g., `ACC` or `PRD`) as needed:
+   Use the `Connect-IDNW` command to authenticate using secrets from the registered Key Vault. Specify the `-Instance` parameter (e.g., `DEV`, `TST`, `ACC` or `PRD`) as needed:
 
 
    ```powershell
    # Using generic environment variables
    Connect-IDNW
 
+   # Using instance specific environment variables (DEV)
+   Connect-IDNW -Instance DEV
+
+   # Using instance specific environment variables (TST)
+   Connect-IDNW -Instance TST
+
    # Using instance specific environment variables (ACC)
    Connect-IDNW -Instance ACC
 
@@ -95,6 +107,12 @@ You can securely store and manage the required credentials in Azure Key Vault an
    Alternatively, you can use instance specific environment variables. If these variables are set, you have to specify the `-Instance` parameter when running `Connect-IDNW`:
 
    ``` yaml
+   IDNW-DEV-BASE-URL
+   IDNW-DEV-CLIENT-ID
+   IDNW-DEV-CLIENT-SECRET
+   IDNW-TST-BASE-URL
+   IDNW-TST-CLIENT-ID
+   IDNW-TST-CLIENT-SECRET
    IDNW-ACC-BASE-URL
    IDNW-ACC-CLIENT-ID
    IDNW-ACC-CLIENT-SECRET
@@ -120,13 +138,19 @@ You can securely store and manage the required credentials in Azure Key Vault an
 
 3. **Connect to IdentityNow using SecretManagement**
 
-   Use the `Connect-IDNW` command with the `-UseSecretManagement` parameter to authenticate using secrets from the registered Key Vault. Specify the `-Instance` parameter (e.g., `ACC` or `PRD`) as needed:
+   Use the `Connect-IDNW` command with the `-UseSecretManagement` parameter to authenticate using secrets from the registered Key Vault. Specify the `-Instance` parameter (e.g., `DEV`, `TST`, `ACC` or `PRD`) as needed:
 
 
    ```powershell
    # Using generic secrets
    Connect-IDNW -UseSecretManagement
 
+   # Using instance specific secrets (DEV)
+   Connect-IDNW -Instance DEV -UseSecretManagement
+
+   # Using instance specific secrets (TST)
+   Connect-IDNW -Instance TST -UseSecretManagement
+
    # Using instance specific secrets (ACC)
    Connect-IDNW -Instance ACC -UseSecretManagement