We are looking to integrate an external OIDC identity provider as a social/external login in our ABP Commercial application, following the Account Pro module documentation (AddOpenIdConnect + WithDynamicOptions). The OIDC provider we need to integrate only supports private_key_jwt as the token endpoint authentication method — meaning no client_secret_basic or client_secret_post is available. The current documented pattern assumes a client secret, which doesn't apply when using private_key_jwt (where the client authenticates by signing a JWT with a private key instead).
Some questions:
Does ABP Commercial have any existing support or documented approach for external OIDC providers that require private_key_jwt authentication?
Is there any planned support for private_key_jwt in the external login infrastructure — for example as part of WithDynamicOptions or the Account Pro module?
If we implement this ourselves via OpenIdConnectEvents customization, are there any ABP-specific pitfalls we should be aware of — particularly around how this interacts with OpenIddict, the Account module's external login flow, and user creation/mapping?
https://oauth.net/private-key-jwt/
Any guidance or pointers would be appreciated.
Thanks
If you are using ABP Suite to generate UI etc, it seems like properties of base classes are never included in DTOs etc and there AFAIK, there is no option to do so either. Assuming it isn't there, this is something that ABP should consider including. This could be either that you can just select the built in properties for addition to the properties you add manually, or that you could perhaps manually add a property with the same name as a built in one, which would then make the built in one be included etc.
To make this a bit more obvious what we are looking for, assume a simple use case like we want to display the CreatedTime of a new record/object in the UI. This property probably exists in all base classes for entities, but to actually do it now, I believe you have to add it manually in all layers. If I am wrong, please let me know how to do it.
Thanks.
We have an ABP app built using the latest version of ABP - Angular for UI. When running the angular app locally against the .Host hosted in an Azure Web App everything works as it should. However, when pushing the Angular app to a Web App (not a static web app for reasons) everything works as well, except that we always get a "An error has occurred! Error detail not sent by server." at first page load. This regardless of which browser etc. This only happens on first full page load, after which everything works as it should.
There are no errors reported whatsoever in server logs, web browser console etc. If it had not been for this error message, you would have no idea that something isn't what it should be.
This happens regardless of if you are authenticated or now (authentication works fine also).
For obvious reasons we can't post any logs as there are none indicating any problem.
How come the logger settings is hardcoded into Program.cs and not in appsettings.json?
AFAIK, this goes against recommendations and best practices, an I fail to see a valid reason for this compared to just putting it in appsettings. This basically requires you to make code changes to modify the logging configuration, and also makes it impossible to have different configuration in different environments?
There have been a few requests about this in the past, none with an answer/resolution as it seems
https://abp.io/support/questions/1496/ABPIO-WASM---Log-level-configuration
https://github.com/abpframework/abp/issues/17333
etc.
Hi,
It seems like ABP Suite has some problems generating CRUD pages for Angular when there is navigation properties.
First, there seem to be no way not to get Navigation properties added to the list view (besides manually removing them afterwards of course). Second, it also seems like the code generated to actually fetch those navigation properties to show isn't working either. So you will end up with unwanted empty columns. If you open the row in Edit mode, everything seem to work fine, including the dropdowns for District and Employer and populated with correct lookup data.
I can't believe this is still a problem in 2026 despite numerous requests for it over the years, but how can you change or hide the footer in the LeptonX theme?
Even having to do this in a commercial product intended to build things for other clients that are not Volosoft is crazy in itself, even more so that AFAIK, you are still required to actually modify code to do so? Or is there now a better way so we can at least hide the footer with simple CSS change? What is the recommended way to get rid of this?
What is the state of the promised fix / new / updated theme so that this won't be a problem and that you can just change the footer settings?
Please just remove this and let anyone who actually actually have a copyright footer implement it themselves.
Thanks.
This is a continuation of this ticket/thread which was closed
https://abp.io/support/questions/8727/New-React-Native--Expo-templates-not-working---multiple-errors
Hello, As you may notice from the template, the new Expo version has been applied, and the overall structure has been updated accordingly. We have also addressed the issues you mentioned. I recommend reviewing the latest documentation, which explains the updated structure in detail: 👉 https://abp.io/docs/10.0/framework/ui/react-native?Architecture=Tiered
If you encounter any other issues, I will be happy to assist further. Thank you for your cooperation.
Glad to see that the React Native / Expo template did get some love in the end with updated code + updated documentation. Also glad that Expo Web is now a first citizen (you recommend running it yourself here https://abp.io/docs/latest/framework/ui/react-native?Architecture=Monolith)
Sadly, with regards to actually using the template for anything but non critical trial and error, things seem to be the same as before. There are outdated packages (like Axios 1.2.1 relesed 11 years ago), unused packages still included, packages doing the same thing included (like native-base and react-native-paper), Javascript and Typescript mixed.
Worse though is that the template STILL seem to be broken out of the box with what appears to be just broken code.
Some examples
This means, AFAIK, that you are still unable to even build the generated React Native / Expo app without first fixing various kind of problems to even get going. Or probably get going I should say, as we decided this time around again that giving the current problems, it just isn't an option to use this for anything intended to be used in production.
This again makes us questioning the foundation for the React Native / Expo template. Despite it being a paid module (it is only available in ABP Commercial AFAIK), it seems like no one at ABP has even tried to generate a new project and make sure it works out of the box. Which makes us question what kind of testing is actually performed on this before a release, as these problems are very obvious.
Sorry for being so negative here but we have been waiting (and paying) for a working React Native / Expo template in ABP for several years now, but we still find that this is a no go for a serious project intended for real world usage.
So we again ask, is the React Native / Expo template actually supported by the ABP team? Is there a plan to actually get it working for some real world projects? Compared to the other templates and services provided by ABP (which are great), this still feels like at best some early beta version, several years after having been released.
What is going on?
The BookStore tutorial for Angular seems to be outdated
https://abp.io/docs/latest/tutorials/book-store/part-02?UI=NG&DB=EF
as it still refers to using modules even though the Angular template does not do that anymore as recommended by the Angular team
yarn ng generate module book --module app --routing --route books
etc.
We find that the basic theme is REALLY basic as the name implies. LeptonX on the other hand feel kind of bloated, very opinionated and based on our our experience, very hard to customize besides very basic CSS stuff. What you see is what you get and if you are not happy with that you are kind of out of luck and have to roll your own
Any plans for a new modern lightweight but easily customizable theme that also works well in mobile view and with Expo / React Native? Any alternatives to the ABP ones?
It seems like the latest version of LeptonX seem to lack the login link when in "mobile mode". It is not under the hamburger menu either.
If you (on a device that supports it) zoom out so you get the non mobile view, you can login and then if you return to the mobile view, you will se the account icon in the mobile nav menu.
