Activities of "Astech"

Morning @ismcagdas,

That's great, thank you very much for your reply.

All the best

Thanks for your reply ismcagdas

We are wanting to implement Microsoft Graph and believe this requires authenitcation through AddMicrosoftIdentityWebApp instead of OpenId does it not? We can get AD working fine and can login users. It is the Graph element that we are struggling with.

Hi @ismcagdas

We don't have the OpenID section of our appsettings enabled or configured as we were under the impression this is configured through this:

As per the instructions in approach 2 here: https://community.abp.io/posts/how-to-use-the-azure-active-directory-authentication-for-mvc-razor-page-applications-4603b9cf?_ga=2.167438713.612361716.1679501585-1726878413.1679501585

Is this correct?

Thank you Scott

Changed our minds and decided to just clear the cache on feature update. This way we get instant change and keep the benefits of the cache manager normally:

We have resolved this by moving the GetEditionValueOrNull and GetEditionValueOrNullAsync methods from the FeatureStore up into the EditionManager. We have then stopped using the cache manager and just doing a call to the repository to get the value everytime. This is getting rid of the cache manager and related issue:

<br>

Thanks @ismcagdas

I have narrowed the problem down to AbpFeatureValueStore. I have moved all methods to our own FeatureValueStore so we can debug and make any necessary changes.

I can see that a cache is being used for the retreival of setting values and I think this may be the issue. Is there a way of disabling this or perhaps forcing a re-get of the value? And would this have any negative effects on perofrmance?

Thanks

Possibly related to https://github.com/aspnetboilerplate/aspnetboilerplate/issues/1433

and https://github.com/aspnetboilerplate/aspnetboilerplate/issues/1574 ?

AppFeatureProvider: Start the app. Change the value to true, then immediately to false again. The value has now dissapeared as expected from database:

On edit of the edition, the value still comes through as TRUE:

It's causing problems. If setting back to the default value, it does not get the value correctly. It's as if the IAbpZeroFeatureValueStore is caching when setting back to the default value.

Restarting the application resolves the issue but this is obviously not a viable solution.

Thanks

Ok, so not just checkboxes. For any setting, when trying to set the value back to it's default value the save does not happen.

Workaround is to remove all default values in AppFeatureProvider which isn't ideal but will do for now.

@ismcagdas - can this be looked into and resolved please?

Thanks