Julian Löffler

Results 46 comments of Julian Löffler

We are using `svcomp-Reach-64bit-Automizer_Bitvector.epf` and the latest release of UAutomizer. If I use the suggested settings: `examples/settings/automizer/MemoryModel/svcomp-Reach-64bit-Automizer_Bitvector4Byte.epf` `examples/settings/automizer/MemoryModel/svcomp-Reach-64bit-Automizer_Bitvector1Byte.epf` UAutomizer will produce an exception: `ExceptionOrErrorResult: AssertionError: de.uni_freiburg.informatik.ultimate.logic.SMTLIBException: Sort RoundingMode not declared...

This C program will produce the wrong result. ```c /* A union which permits us to convert between a double and two 32 bit ints. */ typedef union { double...

``` { "id": "xxxxxxxxxxxxxxxxxxxxxxxxx", "acceptMappedClaims": true, "accessTokenAcceptedVersion": null, "addIns": [], "allowPublicClient": false, "appId": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "appRoles": [ xxxxxxxxxxxxxxxxxx ], "oauth2AllowUrlPathMatching": false, "createdDateTime": "2020-11-30T11:11:54Z", "description": null, "certification": null, "disabledByMicrosoftStatus": null, "groupMembershipClaims": "SecurityGroup,...

I think there is a difference between "sonar community edition" and "sonar enterprise edition". If I start a local sonar instance with the image "sonarqube:9.6.1-community" it can extract the name....

Would be cool to be able to customize the claims responsible for the user's username / display name

Yeah, If you want I can spin up a test instance and create a plain app registration without saml sso attached. On Mon, Aug 29, 2022, 20:32 Michael Johnson ***@***.***>...

I don't think you have migrated your user beforehand e.g. if you have a user `myuser` with external identity `[email protected]` you have to patch him beforehand: `curl -X POST -v...

So actually a different token was used to extract the name of the user. Pull Request #130 fixes this issue for me - can you take a look @srvrguy ?

Until this is possible: You can use the old tables instead of the new ones, just change the panel type to "table-old" in the dashboard's JSON.

Already Exists: https://mattermost.uservoice.com/forums/306457-general/suggestions/10197642-support-openid-connect For us (me and 120 other people) this feature is really essential, without it we might consider another chat application because we do everything with OIDC.