Activities of "dmeagor"

The point is that this is the wrong way around, and I'm guessing by mistake, not by design.

Specific items would always override group permissions. To use a file system as an example, a file permission would override the inherited folder permission. With ABP you have it the other way around which has no use case that I can see.

It should be:

Tenant default permissions are inherited from Edition, but permissions set on the tenant are not overwritten by Edition.

Example. If a feature is causing an issue for a specific customer, we would disable it on their tenant, not the entire edition.

I've been in contact with the author of Rebus and they've confirmed to me that the behaviour is intended.

Connection errors bubble up to the calling app (in this case ABP) and any retry logic needs to be handled there.

https://github.com/rebus-org/Rebus.RabbitMq/issues/98#

If you follow your own link then you will see that the issue was moved to the following issue and then marked as Completed

https://github.com/rebus-org/Rebus.RabbitMq/issues/3

Currently our application fails every time the server is rebooted and there doesn't appear to be any obvious way to correct this from our side.

Is there no way to put a short say 5 second delay and retry loop into the rebus setup code?

• ABP Framework version: v5.3.0
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes

When we do a restart of our production server, sometimes RabbitMq has not yet started, causing the application to never start. I'm not sure if this is something which should be handled in the abp code?

Volo.Abp.AbpInitializationException: An error occurred during the initialize Volo.Abp.Modularity.OnApplicationInitializationModuleLifecycleContributor phase of the module Volo.Abp.EventBus.Rebus.AbpEventBusRebusModule, Volo.Abp.EventBus.Rebus, Version=5.3.0.0, Culture=neutral, PublicKeyToken=null: An exception was thrown while activating λ:Rebus.Internals.ServiceCollectionBusDisposalFacility -> λ:Rebus.Bus.IBus -> λ:Rebus.Config.IBusStarter.. See the inner exception for details.
 ---> Autofac.Core.DependencyResolutionException: An exception was thrown while activating λ:Rebus.Internals.ServiceCollectionBusDisposalFacility -> λ:Rebus.Bus.IBus -> λ:Rebus.Config.IBusStarter.
 ---> Rebus.Injection.ResolutionException: Could not resolve Rebus.Bus.IBus with decorator depth 0 - registrations: Rebus.Injection.Injectionist+Handler
 ---> RabbitMQ.Client.Exceptions.BrokerUnreachableException: None of the specified endpoints were reachable
 ---> System.AggregateException: One or more errors occurred. (Connection failed)
 ---> RabbitMQ.Client.Exceptions.ConnectFailureException: Connection failed
 ---> System.Net.Sockets.SocketException (10061): No connection could be made because the target machine actively refused it.

Seems to be working. Can the Google sign on URL be obtained in anyway so that we can pass it to our front end (static cdn deployed) via an api call? It would be nice to have the button on the homepage.

We could do some hacky iframe thing but I thought there might be a better way.

• ABP Framework version: v5.2.1
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes

When trying to login into an account with Google SSO, when there's an existing email address in the system, it doesn't log in and instead is redirected to the register page.

This is related to this issue: https://support.abp.io/QA/Questions/2852/SSO-requires-the-user-to-register-using-the-login-page

I have opened this ticket on behalf of my developer who still cannot add tickets to this system. More screenshots will follow.

Thanks I'll taker another look, it may be that we have made a mistake with the merging of the IDS MVC pages as we have several overrides setup and may be using some outdates files.

Regarding the flow, I took another bash at designing something that matches how ABP handles tenants.

For standard logins logins I've moved password to a later page once the tenant is identified, either by the custom tenant handler or by the tenant selection page.

Are there any plans to implement a tenant selector page like this? This seems like too much custom code to safely add to our project without causing a security issues if we ever failed to merge changes correctly. If not, any idea how best to approach this?

• ABP Framework version: latest
• UI type: identity server MVC

Abp's SSO implementation is completely broken and requires users to register using the login page. Existing users cannot login by SSO at all. Its a bug that I reported over a year ago and exists on your own website. There isn't even an SSO option on the register page. It is essentially unusable in its current form.

Standard SSO flow would be as below. Do you intend to fix this any time soon, if not how can I do this myself?

SSO authenticated

• single user email exists
  • Login to matching account
• multiple user emails exist
  • display tenant selector and login.
• email does not exist
  • Register new account

Example.

• ABP Framework version: v5.11
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes

To allow our users to close their accounts properly, I set the tenant activation state to Passive, then try to sign them out with OAuthService.logOut, but get the following view. All pages in the identity server MVC show this message until the cookie expires.

Reopening as the bot appears to have closed this issue before resolution.