Many thanks Alper :)
much appreciated
Thank you
HI let me expand on the question
We have a client that wants read only access to five APIs in a system created with ABP Suite / Commercial
What is the simplest way for us to give our client access to these 5 APIs eg with an auth token?
Can we set this up with Identity Server
Guys as always , an amazing project, but sometimes the docs dont cover everything.
big thank you
Jon
PS we know how to use postman , we were not asking ABP tech supprt to teach us postman, we were asking ABP support to help us with ABP ...
Thanks Alper - this was autogenerated, but i will just delete it for now as I dont really need it :)
Alper huge thank you - 36 hrs of head scratching and of course you are right. It was creating the seed database with some localhost settings that was causing the fail.
I still have some issues with browers not logging in, but they go away if I create a new browser profile
I have tried clearing all data for the sites but something in WASM might be caching.
Anyway apart from that (and its just me) we seem to be up and running.
I think you should put together a best practice deployment giude. I guess in hindsite a lot of this is now obvious, but it will smooth the path of future ABP converts.
:)
Thanks Alper
Aha - this helps a lot - will report back
Update - added an extension tgo chrome to ignore x-frame policy but still login fails.
So you may be right about it not being an x frame issue.
But still cannt get a working deployment in azure with two subdomains. Please let us know what yuo think and also where to send logs to
So running blazor in in a virtual app (/blaze) hosted by azure solves the problem of x-frame
I can now login directly
with I can login directly with https://a-----.azuresites.net/Account/Login
and use the site.
BUT getting blazor to run in a sub directory is not smooth and the login route is broken / pluse we have to hard code all the menu items with /blaze/menuItem in blazor
OR should we be trying to host the APIs in a virtual app / subdirectory.
Putting the Host and Blazor on the same sub domain solve half my problems but creates others
Seriously we need better deployment documentaion (unless I have missed it).....
Please Help
Where do you want me to send the logs - can you email me.
Also this is pretty high priority for us now - please can you escalate this up at ABP
This is why I paid for support - this is my time of need please
I think its because of the x-frame same origin issue I pasted. On local it is friom the same origin (different ports). but now the sites are on two different subdomains so xframe same origin policy kicks in.
When you host this on Azure do you have two different sub domains or do you put the apis in a virtual app / subfolder ?
