I'm looking for inormation on LinkToUser as used in the Test "UserAppServices_Link_Test.cs".
In the sources and documentation, there is not a single word explaining what it is :-) https://aspnetboilerplate.com/api-docs/html/Properties_T_Abp_Authorization_Users_UserAccount.htm
It looks like it could be for linking an alias-user to a UserAccount even accross tenants? If this is the case, please explain a bit. E.g. which user and tenant is used to store at any given point and its intended Use-Case.
Thanks for infos!
Richard
Hi, We're looking at the ASP.NET Zero Power Tools Entities and they appear to work as intended. Any way to add a feature to delete the files and dependencies created if desired? An "undo" would speed the agile process a great deal. Else, we'll stick with GIT branches and stashes. Other ideas? Thanks.
Thanks. Yes, I'll put a breakpoint and debug this when I can ... this is a POC I wanted to get working, but not top prio with aspnetzero here at the moment so can't say. Thanks again.
Thanks Alper,
Yes. I have not modified that file, and the admin GUI on the mobile works fine, where I can also define a tenant and a user. But as soon as I try to login as that user, I get the error above. There is some funky manipulation of ports going on somewhere in the original source code (no mods by us), and it doesn't work :-)
Dear alper, OK, this may be another problem, but do you have any idea where these port numbers are comming from (see screen shot). I have not changed anything in the mobile app, and the user-login connections are now failing due to ports that do not exist. A search through all files did not lead to any clues. THANKS
Thanks alper. It was not a communication error. It works fine if I use .Web.Mvc as the target instead of Web.Host. I have been using host the whole time, since that is what it says to use in the documentations. All of this above, and always using Web.Host. The APIs it was failing on are not available on Web.Hos, so the connection was made, and then the API not found which responded with internalServerError...
Thanks again for your help. Moving on.
Thanks! But how can I authenticate the app when it never starts? I never get a chance to authenticate, since the app never gets past the init screen before it crashes. Have deleted all bin/obj and created new android emulators, so a "stale cache" cannot be the problem.
Thanks for any tips!
Hi alper. Many thanks. This helps. I am indeed NOT getting that response. I'll investigate and get back to you here...
From your log above:
INFO 2018-09-26 12:44:07,334 [9 ] uthentication.JwtBearer.JwtBearerHandler - Successfully validated the token. I'm thinking that this may be where the problem is in my case. How does the mobile client get a valid token without logging in first? Hmmm.
Thanks alper. Yes, see my first post. This is precisely what I did. That is not the problem. Also above, you can see in the log/stack that the connection is working fine.
The problem, I think, is that it is not finding the following route -- and I don't see it in the code either:
http://192.168.2.107:22742/AbpUserConfiguration/GetAll
So my questions above are still the same. Can you help me out with them? THANKS!