Hi Maliming,
it was good to have an example on how to do it using mvc, I have the same need and cannot find a proper example.
Thx
Hi @gterdem,
thank you for your help and reply but I still did not manage how to bypass the need to choose the tenant but not using the domain resolver.
In the login page, how can I hide the tenant selector ? On the customization of the login, there is nothing related with the tentant selector but it is shown.
Another thing, how can I use a combination like this: http://localhost:12345/Account/Login?tenantid=1
This way in the url I could define the tentant I wanted to use on the login.
I need to have a customized login for each tenant, with diferent layout based on the tenant that was previously passed on the url, and that the tenant selector is hidden from user.
This was a great help if you can manage to prepare me an example.
Thanks
Hello @gterdem,
I understand your explanation, but what I don't understand is why the login is independent or can be included as option like in Asp.Net Zero.
The identification should be possible to do within the angular or mvc or blazor project on my idea.
I know that we need to authenticate and validate the token to be able to use the services, but why not be able to do this inside the client project and needed to make this authentication thru another application and then return to prior page or redirect to another ?
Thanks, Paulo
Hi,
how can I make the login without using the redirect url and login from another port or identity server ?
When using Angular or MVC or Blazor version I want to be able to do login and enter the application without redirecting to a login service that will then redirect me to the homepage.
I need to have a personalized login for each tenant and not the same login for each application.
How can this be achieved ?
Paulo
On my side no.
Is it possible for me to share with you the project so you can test the way I have and see what's wrong with it ?
It's several days wasted and could not move on because of something that should be simple but in my case, is not.
Hi,
it's not a chrome related problem, i tried the link you've sent and the problem is the same.
I've tested deleting the database, changed the appsettings on Dbmigrator and run it again.
Problem is the same.
Did you tested following the example i said to simulate on your side ?
" abp new TestApp --template app-pro -csf -m react-native --preview -cs "Server=..." --tiered
do the migration
change appsettings.json on IdentityServer to be http not https and localhost to your local ip do the same on Properties/launchsettings.json
change appsettings.json on HttpApi.Host to be http not https and localhost to your local ip on AuthServer section and set RequireHttpsMetadata to false change Properties/launchsettings.json to http and localhost to your local ip
run the identityServer project and try to login "
Hi Liang,
the problem is not related with chrome, the problem it's easy to reproduce on your side:
create the project with the command:
abp new TestApp --template app-pro -csf -m react-native --preview -cs "Server=..." --tiered
do the migration
change appsettings.json on IdentityServer to be http not https and localhost to your local ip do the same on Properties/launchsettings.json
change appsettings.json on HttpApi.Host to be http not https and localhost to your local ip on AuthServer section and set RequireHttpsMetadata to false change Properties/launchsettings.json to http and localhost to your local ip
run the identityServer project and try to login
it will not give error or wrong password, just simply does not enter.
it's not related with chrome, the problem is the same on any browser.
react-native will not work also because of this issue, neither any project.
if you do the same not using the app-pro but app template, it works well.
there is one warning on terminal:
The cookie 'XSRF-TOKEN' has set 'SameSite=None' and must also set 'Secure'.
@alper i did not upgraded, it's a clean project creation using the following command:
abp new AppTest --template app-pro -csf -m react-native --preview -cs "Server....." --tiered
the project is created and i change all references https to http on appsettings and properties and localhost to local ip.
when trying to use de identityserver, cannot log in, does not give error but also does not enter.
when trying to use react native, does not work.
if the project is based on the template app and not app-pro, it works well with the changes.
Seems in github there was a comment that on the night build of 4.1 version or preview version this is solved ? Is it ?
How can I use it to test it ? and when will be released the final version of 4.1 ?
Thanks,
Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.
Using the app-pro template, setting https and localhost urls to http and fixed ip, to be able to use react native project, identityserver is unable to login and creating the cookies that are necessary to work with anything.
the AntiForgery seems to work well under https but when using http, it's not working at all.
Since it's demanded on react-native project to use http, how can this be solved ?
Thanks
Hi,
When I change the project to use http instead of https and change all localhost to my local ip, when i try to login on IdentityServer it does not give wrong password error but does not identify itself, does not store any cookie and shows again the login screen.
I need to use http and local ip in order to be able to test react native project. Since it does not like the self signed https local server.
The project was working well using localhost and https.
What's missing ?
Paulo
