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
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,
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
The main issue is that i do not have a running version, so it's a installation problem still.
Hi,
Any prediction when it will be released ? I'm under pressure to make a presentation and need that working.
Done the upgrade to RC4, done a new project.
Problem is the same:
Here is the error that show in command line:
You need to wait for Font.loadAsync to complete before using the font.
We recommend loading all fonts before rendering the app, and rendering only Expo.AppLoading while waiting for loading to complete.
node_modules\react-native\Libraries\YellowBox\YellowBox.js:63:8 in console.error
node_modules\expo\build\environment\muteWarnings.fx.js:27:24 in error
node_modules\expo-font\build\Font.js:18:16 in processFontFamily
node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer-dev.js:3683:38 in diffProperties
node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer-dev.js:3694:8 in diffProperties
node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer-dev.js:4109:29 in createInstance
node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer-dev.js:15835:12 in completeWork
node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer-dev.js:19409:28 in completeUnitOfWork
node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer-dev.js:19380:30 in performUnitOfWork
node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer-dev.js:19347:39 in workLoopSync
node_modules\react-native\Libraries\Renderer\implementations\ReactNativeRenderer-dev.js:18997:22 in renderRoot
Network Error
The above error occurred in task fetchAppConfig created by takeLatest(app/fetchAppConfigAsync, fetchAppConfig) created by _callee created by rootSaga Tasks cancelled due to error: takeLatest(app/fetchAppConfigAsync, fetchAppConfig) takeLatest(app/setLanguageAsync, setLanguage) takeLatest(app/logoutAsync, logout)
Hi,
seems almost everything is working now, only react native is now giving error and I did not test angular version.
When starting react native on a real android device, it give the following error:
console.error: "You started loading the font "Roboto.medium", but used it before it finished loading You need to wait for Font.loadAsync to complete before using the font. We recomend loading all fonts before rendering the app, and rendering only Expo.ApoLoading while waiting for loading to complete.
What's the solution ?