Answer the question
In order to leave comments, you need to log in
What is the best way to implement frontend under IIS and web services?
There is IIS, on which a bundle of web services (SOAP and JSON) is spinning.
I would like to make a frontend for this case, so that the user can work with web services as a person.
There is also a condition that the user must log in to the domain and tell the services his account (well, or ssid in extreme cases), because he can enter this data or not - it depends on whether his account or domain group is specified in the services backend.
And the question is: what is the best and easiest way to achieve this so that:
A) not to raise a new machine under the frontend, work in IIS
B) it worked not only in IE, but also at least in chrome. That is, the browser can explicitly ask for a login / password, but it would be better for it to transparently recognize the login (the user is sitting on a machine in the domain).
C) it is desirable not to write a backend (I really want to believe that you can get by with one client-side javascript) C
) and attach twitter bootstrap or something similar to this for ease of development
I would be grateful for any ideas, especially regarding the interception of domain authorization.
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question