Hi, Any AppAuth users here? I have implemented a generic support for OpenID Connect using the AppAuth framework for my apps. I have used the easy way of fetching the configuration document from the IDP and let that control the connection. Now I have a IDP that say that we must use client_secret_jwt, and they will not allow anything else. But in the config document they list all available auth methods like this: "token_endpoint_auth_methods_supported" = ( "client_secret_basic", "client_secret_jwt", "client_secret_post", "private_key_jwt") So my client uses the client_secret_basic and later gets rejected. Since I've not used the req auth method. The reason is that they want to phase out the use of _basic and _post, but they have some legacy system they must support. I haven't found anything documented about the logic behind what auth method AppAuth uses, but my guess it starts at the top of the list and uses the first one suggested? Is there a way for me to force AppAuth to only use client_secret_jwt regardless of what the config document say? If anyone know a better forum to ask this, please let me know!

Hi, This is a weird one: We have a iOS project that has CorePlot as a sub-project that builds it's .a file that are linked with our binary. Everything worked fine on Xcode 14.2 but building the projects with 14.3 I get a massive amount of errors of this kind: "Mixing declarations and code is incompatible with standards before C99" That relates to declarations that are not at the top a functions and that has been normal for as long as I have written Obj-C. It only happen in the CorePlot files not in our own. I can't find any special differences between the sub-project and the enclosing projects settings. Since it's has worked for years in all older versions of Xcode, I suspect this is something related to 14.3 and perhaps some older project formats? Any ideas to try? I've already messed with the compiler version settings, but both projects had GNU99 set, and changing it would did nothing...