Kevin Papst

Thanks, I'll check that. But one question anyway: how do you create timesheets that do not follow the rounding rules? Normally it shouldn't be a problem when the rounding is...

Okay, sorry I missed the important part in between about you changing the rounding rules between exporting and re-opening the timesheet. Okay, that is a theoretical problem, I agree. Should...

Wow, okay. Sounds like a broken workflow. Why does your client dictate your rounding rules? No, don't answer that! 😁 I agree that toggling the export flag should not change...

Sorry, you need to provide clear explanations in one post. I don't get what your problem is. If the visibility setting is causing troubles, then this has nothing to do...

Closing 😁

> Content-Security-Policy: That is not caused by Kimai. This sounds like an error caused by the Azure login page. If you use Kimai in Docker, this could be an https...

So with the Apache image? Maybe this could help: https://github.com/kimai/kimai/pull/5071 Its possible that the SAML login sees the http call and cannot detect that it was an https call originally...

I guess you have to add an environment variable to your docker compose, something like ``` kimai: image: kimai/kimai2:apache environment: - TRUSTED_PROXIES=caddy,localhost,127.0.0.1 ```

Can you try without these lines ``` # Define a macro to set the RemoteIPTrustedProxy directive RemoteIPTrustedProxy ${PROXY} # Use the macro, passing the environment variable TRUSTED_PROXIES Use SetTrustedProxy %{TRUSTED_PROXIES}e...

Yes. But Kimai can't properly read the SAML answer or validation fails. And I am almost certain, that it has todo with the reverse proxy, because a direct Azure Entra...