Vandaag werk ik ook thuis, omdat de rest van het team ook thuis werkt vandaag.

Hakan heeft mijn vraag 

"Where can i view the database, redis connections and the config store? to edit/view the data?"

beantwoord en de database connection string gestuurd en gestuurd hoe ik ermee kan connecten. Hij heeft ook de config stores gegeven die ik kan gebruiken om config values toe te voegen of te veranderen. Redis heeft hij nog niet klaar helaas.

Later toen hij bezig was met kwam hij een issue tegen met de redis connectie.
Dit bericht kreeg ik terug

"hi redis connection should be okay, but there is a code chage needed here is the generated message for you ![🙂](https://statics.teams.cdn.office.net/evergreen-assets/personal-expressions/v2/assets/emoticons/smile/default/20_f.png "Smile")

Teams message for the developer

  Hi 👋 LaunchCast API Redis is wired up on the infra side (TST):

  • Cluster: vaultnova-nonprod (Azure Managed Redis, host vaultnova-nonprod.westeurope.redis.azure.net:10000, TLS 1.2, private endpoint only)  
  • App Config key: LaunchCastApi:ConnectionStrings:RedisConnection (label Develop) — KV reference, value resolves to host:port  
  • Container App managed identity assigned to the Redis "default" access policy + has KV get/list — so it can fetch the secret AND auth to Redis via Entra ID

  One code change is needed in launch-cast-backend before this works at runtime. The current AddCacheServices in Infrastructure/InfrastructureServiceRegistration.cs (around line 159) passes the  
  connection string straight to ConnectionMultiplexer.Connect, but the App Config value is just "host:port" with no password — the auth happens via an Entra access token. We follow the same pattern as  
  VaultNova.Web.Api.

  Required changes:

  1) LaunchCast.Api.csproj — add the NuGet package:  
<PackageReference Include="Microsoft.Azure.StackExchangeRedis" Version="3.3.0" />

  2) Infrastructure/InfrastructureServiceRegistration.cs — in AddCacheServices, after ConfigurationOptions.Parse(...), call ConfigureForAzureWithTokenCredentialAsync before Connect:

     var configurationOptions = ConfigurationOptions.Parse(redisConnectionString);

     configurationOptions.ConfigureForAzureWithTokenCredentialAsync(new DefaultAzureCredential())  
         .ConfigureAwait(false)  
         .GetAwaiter().GetResult();

     configurationOptions.ConnectRetry = 3;  
     configurationOptions.ConnectTimeout = 10000;  
     // ... keep the rest of the existing settings

     return ConnectionMultiplexer.Connect(configurationOptions);

  Reference implementation (gold standard): VaultNova.Web.Api/Infrastructure/InfrastructureServiceRegistration.cs → AddCacheServices, around line 277. Same pattern, copy-paste safe.

  Why no password in the connection string: access keys are disabled in favour of Entra ID; the SDK call above swaps the password placeholder for an MI-issued access token at connect time and refreshes  
  it automatically. Locally (docker-compose redis), DefaultAzureCredential will fail to get a token — for local dev we can either (a) keep a password in user-secrets so Parse picks it up and the  
  Configure... call is a no-op when a password is already set, or (b) gate the Configure... call behind an environment check. Let me know which you prefer.

  After the change is merged + a new image is deployed to TST, no further infra steps are needed."

Ik heb aangegevn hier later naar te kijken, maar het maakt voor hem niet zoveel uit.

Ik heb Aycan een bericht gestuurd over extra informatie die ik nodig heb voor mijn eindverslag.

"Hey Aycan,

for my end-document I need a bit more information. 

I need to know the following and I think you guys can answer this the best.

--------------------------------------------------------------------------

I have the org gram from before but maybe it is updated in the mean time? If you have a updated version?

The mission, Vision, goals of the organisation of vaultn?

which services or products vaultn delivers exactly?

for which clients or customers is work performed?

Description of information systems and business processes

- for a overview all information systems  and business processes in the company"


dit was een reactie op:

"Hey Justin, I received your email. Regarding your last question, the information I can share about the company is limited, as we are bound by an NDA. This means we cannot share details such as our strategy, business plan, or information about most of our partners, as these are not publicly disclosed.

Could you please clarify what kind of information you are specifically looking for? If you provide a bit more detail, I’ll do my best to assist within the boundaries we have."

van eerder, omdat de informatie die ik mag delen relimiteerd is.

dit was het antwoord op die vraag:

"Hey Justin, I was off last Friday. Let me check your questions and get back to you this week:)"