Activities of "mac"

Trying to run the fresh instance,  and logging into http://localhost:22742/Ui/Login results in a redirect back to the same screen. Breakpoints show successful login via manager and services.

@maliming, we are on version 8.

In a brand newly downloaded instance of the system (Angular and ASP.NET Core), there are 34 instances of localhost (via search) in the solution. And another 12 in nuget packages related to the solution.

Setting aside the references for the angular app (4200), web public, and production/staging, there appear to be 5 distinct ports in use across 7 instances of the use of the word localhost related to running web:

• 57741
• 57743
• 62114
• 22742
• 5000

Our current goal is to move (for development) to 44305 for asp.net core, and 4205 for angular.

What are causes for the /AbpUserConfiguration/GetAll failing like this?

It's highly frustrating that this stuff seems so hard to keep stable with 'simple' changes.

Here's the current state:

1. We've been just trying to get the base ANZ 8.0 application working consistently for almost a week now. That's a lot of time in a solution that is meant to shorten time to market. We have done no customization, other than things to get the base solution working (such as adjusting the ports)
2. We have the ASP.NET Core applicationURL (.NET), as well as the remoteServiceBaseUrl (angular) set to: http://localhost:22742/
3. The Angular solution is being served on http://localhost:4205/
4. Going to the angular solution in a browser, results in the following: http://localhost:22742/AbpUserConfiguration/GetAll?d=1575126211669 being 404 and not found
   1. Where is this call at?
5. Going to http://localhost:62114/.well-known/openid-configuration results in connection being refused
6. Changing to other ports for the discovery document doesn't help either.

Note, we are able to access the Swagger UI and get results for example GetTenants, returns the Default tenant with various attributes under the items array.

We're looking at using an ASP.NET Zero project as a central Identity Server for other projects. We have the latest one (8) with Core/Angular as separate projects.

We're unable to locate the discovery document in the running applicatoin, and the links/images from the following link aren't working:

https://docs.aspnetzero.com/en/aspnet-core-angular/latest/Infrastructure-Core-Angular-Identity-Server4-Integration#testing-with-client

Can we get some guidance?

Thanks, //mac

We're completely blocked by this issue, what can be done?

Uncaught TypeError: Cannot read property 'toLowerCase' of undefined at rm (main.59aa48947dbf150152e1.js:1) at main.59aa48947dbf150152e1.js:1 at t.invoke (polyfills.b90e79c26d150fdebb27.js:1) at Object.onInvoke (main.59aa48947dbf150152e1.js:1) at t.invoke (polyfills.b90e79c26d150fdebb27.js:1) at e.run (polyfills.b90e79c26d150fdebb27.js:1) at e.run (main.59aa48947dbf150152e1.js:1) at e.bootstrapModuleFactory (main.59aa48947dbf150152e1.js:1) at OA (main.59aa48947dbf150152e1.js:1) at Module.zUnb (main.59aa48947dbf150152e1.js:1)

For us, the projects are developed separately, and then merged at the end. That compiled solution being deployed is around 46 megs, not sure it will fit in email.

FWIW, we haven't changed anything at all, first efforts are around CI/CD :)

We're intending to use our first instance of ANZ to manage tenants and their applications that are separate from this instance. This means we want to be able to view tenants, manage their subscriptions, etc. But we don't want this instance to be multi-tenant.

From what I can tell, to do this, we'll need to enable the tenant management screens, but disable any form of actual multi-tenancy (such as separate databases, etc.)

What should we look at for that?

Thanks, //mac

I'm having the exact same error, this is a first time deploy. In this case, it's self hosted, and the angular application is in the same IIS web app.

This is with ANZ 7.0, Windows Server 2016.

Yes, specifically Octopus Deploy. This means that once the application is built, it will be deployed to separate locations (something like qa.appname.com, demo.appname.com, etc. ).

That document didn't seem to go quite that far.