VNG-Realisatie/ODS-Open-Raadsinformatie

iBabs - Toegangsprobleem bij sommige agendapunten

jdevroed opened this issue · 1 comments

Bijvoorbeeld: https://opendata.ibabs.eu/api/informatieobjecten/1cee9c81-674c-4d36-910f-61dd7ba4409b

Deze output:

System.UnauthorizedAccessException: The user is not allowed to view the document with id '1cee9c81-674c-4d36-910f-61dd7ba4409b'.
   at iBabs.Handlers.Public.PublicDocumentHandler.GetDocument(GetDocumentRequest request)
   at iBabs.Public.Api.Controllers.DocumentController.Get(Guid id) in C:\TFS\iBabsPublic\iBabs.Public.Api\Controllers\DocumentController.cs:line 85
   at lambda_method(Closure , Object , Object[] )
   at Microsoft.Extensions.Internal.ObjectMethodExecutor.Execute(Object target, Object[] parameters)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncObjectResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeFilterPipelineAsync>g__Awaited|19_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope)
   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger)
   at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
   at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)
   at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider)
   at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)

HEADERS
=======
Accept: */*
Accept-Encoding: gzip, deflate, br
Connection: Keep-Alive
Host: ibabs-opendata-api-app-svc-01.azurewebsites.net
Max-Forwards: 10
User-Agent: PostmanRuntime/7.26.8
Via: 1.1 Azure
X-Api-Key: 10DAFA63-096D-4716-A2CA-29CEB3920C6D
ibabs-site-name: hoorn
Postman-Token: 75c3c46f-9ab7-440e-aef3-1e51b23d303c
X-Forwarded-For: 213.10.219.132, 147.243.84.77:22362
X-Azure-ClientIP: 213.10.219.132
X-Azure-Ref: 0vKb1XwAAAAApN8aqVgcERZBrcOhF8761QlJVMzBFREdFMDQxMgA2NjhiMzNkOS02MTgwLTRjODktOGZiOC1mZTA4ZDRmNTlhYTk=
X-Forwarded-Host: opendata.ibabs.eu
X-Forwarded-Proto: https
X-Azure-RequestChain: hops=1
X-Azure-SocketIP: 213.10.219.132
X-Azure-FDID: 668b33d9-6180-4c89-8fb8-fe08d4f59aa9
X-WAWS-Unencoded-URL: /api/informatieobjecten/1cee9c81-674c-4d36-910f-61dd7ba4409b
CLIENT-IP: 147.243.84.77:22362
X-ARR-LOG-ID: 77cfb502-9139-46a8-81fd-c145c516a0a6
DISGUISED-HOST: ibabs-opendata-api-app-svc-01.azurewebsites.net
X-SITE-DEPLOYMENT-ID: ibabs-opendata-api-app-svc-01
WAS-DEFAULT-HOSTNAME: ibabs-opendata-api-app-svc-01.azurewebsites.net
X-Original-URL: /api/informatieobjecten/1cee9c81-674c-4d36-910f-61dd7ba4409b
X-ARR-SSL: 2048|256|C=US, O=Microsoft Corporation, CN=Microsoft RSA TLS CA 01|CN=*.azurewebsites.net
X-AppService-Proto: https
X-Forwarded-TlsVersion: 1.2

Dit issue is vorige week opgepakt en is opgelost. Deze kan opnieuw getest worden.

De genoemde url blijft nog steeds dezelfde melding geven. Dit komt omdat dit geen geldige url is. Bij het tonen van een agendapunt kwamen er soms document id's bij dit niet klopten.