Yes I notice that app brings me to the mydomain.com address but that domain is totally different domain. {subname}.mydomain.com is for clients (for app) mydomain.com is for company not for host tenant. (Null tenant) it seems someone else suffers from the smilar problem; #5482
To sum up; I do not want to use bare domain for host. I need any other sub (does not matter the name) as host because DNS records for mydomain.com and *.mydomain.com are also different . these are out of my control.
I have just managed to login by writing any non-existing subdomain like blabla.mydomain.com/?gotolinkedaccountID (or something lke that) it works manually but it should go with properly or there should be a way to do it? any help or idea?
it is resolved somehow. I do not know to reason but issue is not valid anymore.
any implementation like explained at <a class="postlink" href="https://damienbod.com/2017/12/30/using-an-ef-core-database-for-the-identityserver4-configuration-data/">https://damienbod.com/2017/12/30/using- ... tion-data/</a> this seems a full implementation but I need just to save client info to db.
regards, Tugrul
I think I have found a solution for this scenario, I need to authorize client with user password not client password. I mean not with this (<a class="postlink" href="http://docs.identityserver.io/en/release/quickstarts/1_client_credentials.html">http://docs.identityserver.io/en/releas ... tials.html</a>)I need to authorize with <a class="postlink" href="http://docs.identityserver.io/en/release/quickstarts/2_resource_owner_passwords.html">http://docs.identityserver.io/en/releas ... words.html</a> (resource owner not client)
So I'll define an API user on Host (not on a tenant) and I'll set tenant during operation by requirement)
resolved at the github issues section.
any improvements or implementation guys?
project created with aspnet zero v 5.3.0 at 16.04.2018
any tip or help would be great.
