I understand it was not possible to use Windows Integrated Authentication in Silverlight 2.
(See related question).
Does anybody know whether it's possible in Silverlight 3?
I'm afraid it's not, the authentication options in SL3 are the same as I mention in the related question you link to and TransportSecurityWithMessageCredentials I mentioned didn't seem to make the cut for SL3 rtw afaik which is a shame
Related
I am faced with a project that uses custom authentication via a WCF service that returns a set of claims based on some data identifying a user, close to user name and password. Then on top of this, I have a custom STS, derived from Microsoft.IdentityModel.SecurityTokenService, that resides in an ASP.NET web site project. This project looks like it was created with the VS2010 template, and not carefully had-crafted.
My gut feeling, and lots of on-line advice tell me that this web site STS project is very far from production ready. I am now looking for an MVC based STS that I can use in anticipation of being production ready. TinkTecture's IdentityServer looks promising, but it is so much more than simply implementing a custom derivation of SecurityTokenService, I have no idea where to start. If somebody could steer me toward an open project or walk-through that does this, or offer some guidance as to where and how I can start extending or modifying Identity Server, that would be great.
Have you looked at Thinktecture.IdentityServer v3? I'm at the moment using it and very simple to use.
It is still in Beta but RTM will be available soon. It has good documentation and samples too.
https://github.com/thinktecture/Thinktecture.IdentityServer.v3/wiki/Getting-started
https://github.com/thinktecture/Thinktecture.IdentityServer.v3/wiki
Update:
Identity Server 4 is also available. It supports cross-platform deployment with .NET Core.
https://github.com/IdentityServer/IdentityServer4/
Have you looked at the MSDN article by Michele Leroux Bustamante?
It's a little old and based on WCF, but it has code accompanying it.
Building A Custom Security Token Service
If you want ASP.NET based example, Microsoft published this:
ASP.NET Security Token Service Web Site
There's also this STS project on CodePlex.
I was wondering if somebody could answer my questions as I have not used JTAPI before.
I am working on a project where the requirement is to click a link on the MVC website and integrate the call to AVAYA phone (i.e. make phone call using handset via the website)
I have also looked at the Microsoft TAPI but looks like there is no integration with Avaya available with TAPI.
Does anybody know how can I use JTAPI with .Net MVC ? I was assuming it would be an API which I can call from my website but it looks more complicated then it sounds.
Please suggest :)
You may use Avaya DMCC. It has an implementation for .NET
But beware the Avaya licensing policy! DMCC may require extra licenses.
To use JTAPI from ASP.NET you have to use Java classes from .NET
Can you use Java libraries in a VB.net program?
http://www.codeproject.com/Articles/13549/Using-Java-Classes-in-your-NET-Application
I would suggest create an Applet in JTAPI and then integrate in any webapplication whether php,.net I recently did the same thing for my PHP web application.
As #Krishna said with an Applet you could designe your solución, designe that i used to do... Buut now and Day Applets have less support over browsers and they have be come a problem than a solution. The way that i found to solve this issue was use HTML5 with Websocket. In this way i create a Windows Service or daemon (for Linux) to handle JTapi session and create a websocket server Layer, and implement the websocket to create the view int he Asp.net view.
Avaya AES does expose a basic web api providing some basic functionalities which you can call directly from your MVC application, but if you need something more advance, then arguably the best solution would be to build a small Java servlet which you will host on something like Tomcat or JBoss which will expose a SOAP or REST API, which you can call from your MVC app.
I'm curious how SPDY should be implemented when using an ASP.NET MVC application. As far as I know it is not the case by now, but should I wait for an updated MVC (5), new IIS-server, upgraded .net-framework, or something else?
My understanding of this question is "can I use spdy with my IIS based server and .net application".
As I understand it, IIS would need to implement the protocol, and/or a third party would need to offer a module for IIS that implements this. So far, I have not found either of these, but will update my answer if I do.
I need to add social media login capabilities to a site and got stuck a bit, mostly because of the, more or less, non existing beginner documentation regarding these two.
I grasped the basics of DotNetOpenAuth by checking nerddinner but some here suggest WIF so I started looking into it. I realized quickly that just getting clear info explaining if this is feasible at all on shared hosting was not easy. I don't really want to pump through all reference knowledge, technical overviews (checked some out anyway), but just to be able to see the basic functionality.
So my questions are:
Where can I find any tutorials showing the basics and bare minimums needed for WIF to function in an explanatory manner? Preferably setting up WIF in a single MVC site combined with local authorization. Is there any step-by-step documentation at all?
Is WIF feasible, at all, on a single site or would the best option be to find other solutions like DotNetOpenAuth or use the separate APIs? When trying to get to the bottom of this, I have only found information regarding the value of WIF in large, multi-application, and platform environments combined with AD / ADFSv2. Which is completely outisde the bounds of what I need.
When I look at information on WIF, it's mostly linked to ADFSv2 and STS. Is this possible to implement at all for deployment on shared hosting for example?
Any input on the matter is appreciated.
WIF - see the How-to section here.
Also Get Started with Windows Identity Foundation (WIF).
Your best bet is probably to use WIF / ACS. Good link here or look at Windows Identity Foundation (WIF) and Azure AppFabric Access Control Service (ACS) Content Map.
The other way is to add OAuth2 to a custom STS. Refer Identity Server for a really good example of this.
DotNetOpenAuth definitely works on shared hosting, and requires no set up on the web server at all (it's just a .dll in your web site's Bin folder). Depending on the social networking sites in particular that you want to hook up to, it can be just a few lines of code to wire everything up if you're hooking up to OpenID enabled sites.
If the sites you're hooking to use OAuth or OAuth 2, there is more code to write for each individual site to work against their particular proprietary API, but that would also be true for WIF unless they have code to support specific web sites that happen to align with your own.
As a dev team, we're looking to switch to asp.net MVC and I've heard rumors about IIS 6 not being able to support all of the MVC functionality. Is this true? Is there any official set of functionality supported in IIS 7 vs IIS 6? Should we completely avoid running it on IIS6?
You do not loose any functionality of ASP.Net MVC; however, you have one of two options. You can either define an extension on your URL's which will allow you to set up mapping. So for example:
www.example.com/books/computer/list
might become:
www.example.com/books.mvc/computer/list
You can use any extension you want so long as you map to ASP.Net. I am currently using .aspx which meant I could avoid changing IIS configuration at the sacrifice of having extensionless URLs.
The other option as mentioned is using a wild card mapping. What this does is route all requests to ASP.Net. Even requests for static content such as images. This does have a negative effect on performance that you will want to measure. There are ways around this, I believe such as placing all your content in a specific virtual directory that you turn off the wild card mapping for, but I haven't fully explored that option.
I think the issue with IIS6 is extensionless URLs that you can easily achieve by adding a wildcard ISAPI map in IIS configuration.
So, no. While I love IIS7 integrated mode and strongly recommend using it, you won't lose functionality using it. I've deployed several ASP.NET MVC 1.0 projects on Windows Server 2003/IIS6.
Url rewriting can help you to solve the problem. I've implemented solution allowing to deploy MVC application at any IIS version even when virtual hosting is used.
http://www.codeproject.com/KB/aspnet/iis-aspnet-url-rewriting.aspx