Hi,
If you havent updated your organization license, the api key shouldn't be changed.
If you have permission, you can copy your organization's api key from the following page: https://abp.io/my-organizations
Hi there,
Thank you for reporting this issue. You provided as a good scenario. I deliver this case to our team. We will enhance our session management logic according to your case to ensure better security.
We appreciate your feedback and patience as we work to improve the system.
Can you provide us *.abpsln file of your solution? There can be a problem in that file maybe
Hi,
I delivered this issue to our ABP Studio team with an internal issue for this. If more information is needed, they can ask in this issue.
Your ticket is refunded.
Hi,
Nuget servers seem operational right now. Does the problem still exist?
Normally, when you downloaded a package once, it'll be stored {currentuser}\.nuget\packages\ folder locally and won't send request to server, packages will be used from cache.
Does this mean every time we update projects to new version we also have to update Nuget.Config with new nuget urls from abp ?
If your apikey isn't changed, you shouldn't update NuGet.Config again and again. Can you restore packages when you create a new project properly?
Can you try UserFriendlyException instead of Exception?
[Authorize(TappPermissions.TappOrganizations.Delete)]
public override async Task DeleteAsync(Guid id)
{
var users = await _tappOrganizationUsersAppService.GetListAsync(new GetTappOrganizationUsersInput()
{
TappOrganization = id,
MaxResultCount = 1
});
if (users.Items.Any())
throw new UserFriendlyException("This organization can't be deleted because it has users associated with it.");
await _tappOrganizationRepository.DeleteAsync(id);
}
As far as I understand, login operation is not your problem right know, you want to initialize blazor wasm as far as soon, right?
I can suggest you try PWA configuration for your app, pre-configured service-worker caches all the .dll files and makes blazor wasm initialization at second visit to website so much faster. You may try this approach and even it won't satisfy, then you can try implement your own login page as my suggestion for now
Hi @maria_ruiz
In the current Volo.Account and Volo.Account.Pro modules does not implement blazor login pages. It uses Code Flow with OpenID Connect.
Only Angular application has an implementation for Resource Owner Password Flow but it's not enabled by default, developers should implement a related pacakage that brings those login/register account pages. Since it's not secure and not a recommended way, all of applications are pre-configured to use OpenID Connect Code Flow approach. If you need, you can implement blazor components for login and use an existing OpenId Client C# library such as IdentityModel.OidcClient to connect to the auth server.
As far as I understand, login operation is not your problem right know, you want to initialize blazor wasm as far as soon, right?
Nuget servers seem online right now. Can you check if problem still exist?
By the way;
Did you make any changes in your NuGet.Config file? You may check your NuGet.Config file for custom package resolution options, it's configured to use a custom mapping by default for better performance. It may cause som issues, if you can't solve the problem, you can try removing the following section:
As I understand you'll implement it by using angular client right?
If yes, your backend code, in your case it's HttpApi.Host, that project should use Volo.Payment.Web package. After using that package /Payment/GatewaySelection page will be provided by your backend application and redirect your angular client to that endpoint, this endpoint automatically redirect if only stripe configured in your system, if not, it lists all the payment providers to choose.
You already returned it, this will be used to send user to stripe payment page and handle callbacks:
