ok thanks for the info
The admin role is public? What does that mean?
I am using HTTPS
I still had to make the above code change to get it to work
I had this problem today--affected both HTTP and HTTPS in absolute latest version of Chrome
Firefox was OK but still complained in console warnings about SameSite cookies
I implemented the above code change as recommended by liangshiwei and it seems to have corrected the problem
Is the recommended code change a permanent solution or only a temporary workaround?
Hi alper,
I'm not sure about that.
You say the console application in the Acme demo calls authenticated endpoints, but if it does do, the way it does it is buried in your assembly internals.
In the code example you provided above, the access method is via services that are injected into the application from your internals.
For example, IProfileAppService is located in assembly Volo.Abp.Identity.Pro.Application.Contracts
I don't see how this relates at all to Identity Server/Client Credentials, which was the original recommendation made by liangshiwei above. My version of the "console application" is an AWS Lambda and I don't want to have to load it up with assemblies, etc. I want a nice, lightweight client that uses a standard toolset like HttpClient.
Are you sure we're still talking about the same thing?
No, I wasn't able to make it work. After almost 2 days of trying everything imaginable twice, I was forced to implement API key authentication instead.
I think the problem was with the attribute on the API method (i.e. like [Authorize]) and/or with the permissions setup (client, "API resources", etc).
I'm sorry, but the documentation and provided support was quite insufficient.
I'd be interested to see a working example, but then ideally you would also need to show how the Identity Server client is configured. That's a data thing so screenshots of the UI would be good.
OK, thanks for the info. This looks like a good workaround.
This is a vitally-needed feature. It is too awkward to "share" entities by digging around in the file system. They need to be able to be saved in version control and thus need to be inside the solution folder.
I was referring to the browser cache, post-upgrade, on first run of the application.
The "Nuget cache" (Packages folder, etc?) didn't seem to be a problem.
When I use ABP Suite to create an entity, how can a different developer use ABP Suite to work with the same entity? Are the entities saved with the SLN somehow?
