Description

Timeouts in plugins are typically 30 seconds and core cancels after 30 seconds, which means we produce errors instead of failing more gracefully.

Add timeoutsetting per plugin dataset (EvidenceCode model) and override default 30 second cancellation from core in evidenceharvester

Additional Information

No response

Tasks

No response

A few of the post deploy tests are currently failing because of amongst other things not fulfilling the tokenrequirement options.

These tests are good candidates for negative tests anyway :)

Polly's made larger changes to their API in their SDK from version 7 to 8. Upgrading to V8 doesn't immediately require any changes, however how some policies are configured should be updated to be done the V8-way.

Polly has a migration guide from 7 to 8: https://www.pollydocs.org/migration-v8.html

I don't think this is urgent, however it should be done sooner rather than later as I would presume that when they go to V9 they won't support v7 methods anymore.

Description

Maskinporten's VER2 environment has reached EOL and has been removed. We no longer need to support more than 1 test environment (namely, test), so the settings and code should be removed (maskinportenauxurl and maskinportenauxwellknownurl) leaving test.maskinporten.no as the valid option.

These were introduced in #34 and should be removed from code and terraform.

Additional Information

No response

Tasks

No response

Description

We need to create a self-service test setup for new potential consumers of data from DAN in order for them to test the solution from a developer/technical standpoint

Additional Information

No response

Tasks

• New service context "DAN-test"
• New apim product (only in staging and dev) - DAN-test, with automatic subscription approval
• New scope in test-maskinporten (dan:test), public and available for everyone
• New dataset "DAN-test" in the digdir plugin that returns something
• Explain how this is used under testing

Description

When requesting consent the person/organisation must exist in Altinns databases. When they don't it just fails with a generic error.

"person/org xxxx cannot receive consent requests in Altinn" or something along those lines. Filter if ssn.

Steps To Reproduce

Request:
{"requestor":"980178986","subject":"998997801","evidenceRequests":[{"evidenceCodeName":"RestanserV2","requestConsent":true},{"evidenceCodeName":"MvaMeldingsOpplysning","requestConsent":true},{"evidenceCodeName":"Arbeidsgiveravgift","requestConsent":true},{"evidenceCodeName":"OppdragUtenlandskeVirksomheter","requestConsent":true},{"evidenceCodeName":"Firmaattest"},{"evidenceCodeName":"Enhetsregisterdata"},{"evidenceCodeName":"Aarsregnskap","parameters":[{"evidenceParamName":"NumberOfYears","value":1}]}],"consentReference":"schibsted-smb","externalReference":"Demo","languageCode":"no-nb"}

Response:
{
code: 1013,
description: "There was an error during an attempt to access a upstream source. The remote server might be down or overloaded",
innerExceptionMessage: "System.Net.Http.HttpRequestException: Server returned error status code: 400, ",
innerExceptionStackTrace: " at Nadobe.Core.Helpers.DelegatingHandlers.ExceptionDelegatingHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) in D:\a\1\s\Core\Helpers\DelegatingHandlers\ExceptionDelegatingHandler.cs:line 39 at Polly.CircuitBreaker.AsyncCircuitBreakerEngine.ImplementationAsync[TResult](Func3 action, Context context, CancellationToken cancellationToken, Boolean continueOnCapturedContext, ExceptionPredicates shouldHandleExceptionPredicates, ResultPredicates1 shouldHandleResultPredicates, ICircuitController1 breakerController) at Polly.AsyncPolicy1.ExecuteAsync(Func3 action, Context context, CancellationToken cancellationToken, Boolean continueOnCapturedContext) at Microsoft.Extensions.Http.PolicyHttpMessageHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) at Microsoft.Extensions.Http.Logging.LoggingScopeHttpMessageHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) at System.Net.Http.HttpClient.FinishSendAsyncBuffered(Task1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts) at Nadobe.Core.Services.ConsentService.CreateConsentRequest(Accreditation accreditation, List1 evidenceCodesRequiringConsent) in D:\a\1\s\Core\Services\ConsentService.cs:line 324 at Nadobe.Core.Services.ConsentService.Initiate(Accreditation accreditation) in D:\a\1\s\Core\Services\ConsentService.cs:line 92 at Nadobe.Core.FuncAuthorization.<>c__DisplayClass8_0.<<Run>b__0>d.MoveNext() in D:\a\1\s\Core\FuncAuthorization.cs:line 128 --- End of stack trace from previous location where exception was thrown --- at Nadobe.Core.Filters.AzureFilterHelper.Handle(List1 attributes, ExecutionContext context, ILogger logger, HttpRequestMessage request, Func`1 action) in D:\a\1\s\Core\Filters\AzureFilterHelper.cs:line 98",
}

Description

In order to prevent cross-context lookups

Additional Information

            while (query.HasMoreResults)
            {
                foreach (Accreditation accreditation in await query.ExecuteNextAsync<Accreditation>())
                {
                    var listOfServiceContexts = new List<string>();

                    if (!string.IsNullOrEmpty(accreditation.ServiceContext))
                        listOfServiceContexts.Add(accreditation.ServiceContext);

                    listOfServiceContexts.AddRange(accreditation.EvidenceCodes.FirstOrDefault().GetBelongsToServiceContexts());
                   
                    if (listOfServiceContexts.Contains(_requestContextService.ServiceContext.Name))
                        accreditations.Add(accreditation);
                }
            }

Tasks

No response

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update dependency moq to 4.20.72
• chore(deps): update dependency stackexchange.redis to 2.8.16
• chore(deps): update dependency microsoft.azure.cosmos to 3.43.0
• chore(deps): update dependency microsoft.azure.functions.worker.applicationinsights to 1.4.0
• chore(deps): update dependency microsoft.azure.functions.worker.extensions.cosmosdb to 4.11.0
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update sonarsource/sonarcloud-github-action digest to eb21172
• chore(deps): update dependency asynckeyedlock to 7.0.1
• chore(deps): update dotnet monorepo to 8.0.8 (Microsoft.Extensions.Caching.StackExchangeRedis, Microsoft.Extensions.Http.Polly)
• chore(deps): update dotnet-azure-ad-identitymodel-extensions monorepo to 8.0.2 (Microsoft.IdentityModel.Protocols.OpenIdConnect, Microsoft.IdentityModel.Tokens, System.IdentityModel.Tokens.Jwt)
• chore(deps): update dependency microsoft.net.test.sdk to 17.11.1
• chore(deps): update mstest monorepo to 3.6.0 (MSTest.TestAdapter, MSTest.TestFramework)
• chore(deps): update actions/checkout action to v4
• chore(deps): update actions/setup-dotnet action to v4
• chore(deps): update azure/login action to v2
• chore(deps): update github artifact actions to v4 (major) (actions/download-artifact, actions/upload-artifact)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Description

The expectation is that all datasets should appear as normal after deploy and repopulation of the evidencecode cache

Steps To Reproduce

Deploy new core code
Skatteetaten datasets are unavailable until the core cache of evidencecodes is forcibly refreshed

Description

We need to add a "description" field on the evidence value model in order to create better metadata for published data sets.

The field should be included when requesting meta data and omitted when returning the actual values.

Additional Information

No response

Tasks

No response

Description

Support for .NET 6 ends on 12 November 2024—upgrade your Azure Functions apps to .NET 8
You're receiving this email because you have one or more Azure Functions apps that use .NET 6.
In alignment with the end of community support, on 12 November 2024, support for .NET 6 in Azure Functions will end. Your apps that are hosted on Functions will continue to run, but security updates will no longer be available and we'll no longer provide customer service for .NET 6. Learn more about Azure Functions stack version support.

Additional Information

In addition the in-process model will be retired in 2026, so we need to make sure all plugins and functions are running .NET 8 and isolated.

Tasks

No response

Description

Required action
Please migrate all your existing tools and scripts from using the Direct Management API instances to the Azure Resource Manager-based REST API by 15 March 2025. If you have existing instances using Direct Management API, please rely on the Azure Resource Manager-based REST API, which is the standard for all Azure services today. After 15 March 2025, the Direct Management API won’t be supported.

Additional Information

No response

Tasks

No response

Description

This setting can be removed in favour of explicitly setting a default of 100 seconds, allowing plugins to override.

Steps To Reproduce

See hostbuilderextensions.cs

Description

All clients are using maskinporten so certificate support should be removed from api mgmt, code and docs

Additional Information

No response

Tasks

• Apim
• Code
• Docs

Description

test2

Additional Information

test 3

Tasks

No response

Description

The roller dataset is not linked to any servicecontext, but should be displayed somewhere. Are we missing the open dataset connection?

Steps To Reproduce

https://docs.data.altinn.no/datasett/

https://docs.data.altinn.no/tjenester/ebevis/

Description

In order to easier be able to reuse datasets and integrations between service contexts, evidencecodes should support an alias list in the evidence code model.

Core needs to be able to look for both evidence code names and aliases from getavailableevidencecodes when validation requests and also correctly route to the correct name when communication with the plugin.

Additional Information

No response

Tasks

No response

Consider supporting a generic filter/transform mechanism with https://github.com/jdevillard/JmesPath.Net

Altinn 3 app - belonging to testdepartementet to begin with

Authorization requirement is DAGL for an organization
After login present a landing page with options for data.altinn.no servicecontexts retrived from metadata api

It needs a jwk for authentication with maskinporten, clientid with all DAN scopes and apikeys for every servicecontext.

After selecting a context, present all datasets within that context using organization number that the user is currently representing, similar to the poc - each dataset in a collapsible accordion or similar with the possibility to mark them for inclusion in a report. If possible, create everything as generic as possible - using metadata about the datasets to choose how they are presented (key/value, json schema etc) and allow for help texts for each dataset and data element.

Simple button at the bottom for creating a pdf/report of the selected datasets and/or sending to email/altinn correspondence to a given recipient

https://github.com/data-altinn-no/poc-duediligence

Further ahead: inclue dialogporten items for the selected organization to further enhance "my business portal"

Remove belongsto and requirements on open datasets unitbasic, roller, bilpleie, renhold, bemanning, firmaattest, årsregnskap and corresponding datasets in aggregate plugins

Description

The hashtable solution for removing the DAN envelope from dataset responses doesn't work for Tilda because of multiple occurences of dataset values with the same name.
Either we make the envelope subject to an evidencecode flag "AllowEnvelopeRemoval" or we maybe create a tilda model that can be serialised where all the values are contained within a single object. Or we think of something smarter :)

Additional Information

No response

Tasks

No response

Description

Ver2 is being replaced by the new environment "test" in maskinporten so we need to add support for "test" and some time before the end of the year remove "ver2".

Additional Information

(https://samarbeid.digdir.no/id-porten/ny-systemarkitektur/736#overgang_til_ny_systemarkitektur__kva_m_du_som_kunde_gjere)

Tasks

No response

Description

asdsad

Additional Information

No response

Tasks

No response

Description

Make sure steps are run in correct order - deploy-> test, gate and so on - consider making separate workflow for core instead of using the same flow for plugins AND core

Steps To Reproduce

Deploy

Vi må oppdatere cosmos-bruken i Core (det er eneste sted vi har direkte kommunikasjon med Cosmos).

Samtidig burde vi også bumpe til .net 8 på dancore.

Description

Update to version 3 of the Azure Cosmos DB .NET SDK by 31 August 2024
You're receiving this email because you've used version 2.x of the Azure Cosmos DB .NET SDK.

On 31 August 2024 we'll retire version 2.x of the Azure Cosmos DB .NET SDK, and you'll need to update your SDK to version 3.x by that date. Version 3 of the Azure Cosmos DB .NET SDK includes many usability and performance improvements over version 2 of the SDK as well as access to new Azure Cosmos DB features.

Version 3 includes:

Improved performance through stream API support.
Built-in support for change feed processor library and bulk operations.
Mockable APIs for easier unit testing.
Improved diagnostics and observability experience.
Access to new APIs and features including transactional batch, patch, hierarchial partition keys and many more.
Required action
To avoid service disruptions, migrate to Azure Cosmos DB .NET SDK version 3 by 31 August 2024.

Help and support
If you have questions, ask the community experts in Microsoft Q&A or post your them on our GitHub. If you have a support plan and require technical support, create a support request:

For Summary, type Cosmos DB .NET SDK.
For Issue type, select Technical.
For Subscription, select your subscription.
For Service, select My services, then select Cosmos DB.
For Resource, select your resource.
For Problem type, select SQL API SDK – NET.
For Problem subtype, select Error or unexpected result.

Additional Information

No response

Tasks

No response

Description

Create jsonschemas or models that can be used to create json schemas where missing (fregperson, summertskattegrunnlag ++)
so that external clients know what models to expect

Additional Information

No response

Tasks

No response

Quite a few users are confused about how to actually ask for an apikey - provide a few screenshots and a short explanation

Put the pictures and description in this section: https://docs.data.altinn.no/api/#registrere-konto-og-skaffe-api-nøkkel

Description

ConsentReminders should be validated looking at the authcode on the accreditation and not make requests to Altinn

Steps To Reproduce

Post ConsentReminder
Check logs

Description

dfbgdfgfdg

Additional Information

No response

Tasks

No response