Is this issue relating to writing a Relying Party, a Provider, or both? > Relying party

What steps will reproduce the problem? 1. Try to login using Open ID provided by Yahoo in the format of http://yahoo.com/yourid 2. OpenIdRelyingParty.CreateRequest(...).RedirectToProvider(...) throws No OpenId endpoint found exception. 3. Switching to http://me.yahoo.com/yourid successfully workaround this issue.

What is the expected output? Successful redirect

What do you see instead? No OpenId endpoint found exception.

What version of the product are you using? Official build? 2.5.0.8281

Can this problem be reproduced using the included samples?

Please provide any additional information below. Relevant log snippets are superb!

http://yahoo.com/yourid would only work if that was indeed either an endpoint or a page that resulted in a redirect to http://me.yahoo.com/yourid, which in my test just now it did not. There is therefore no way for an OpenID relying party to securely make http://yahoo.com/yourid work as you ask.

There are a few workarounds: * the user types in http://yahoo.com to let directed identity do its work, * the user types in his/her actual identity page http://me.yahoo.com/yourid * yahoo adds identity page redirects at http://yahoo.com/yourid so that it would work. However since that invades their own web site's URL namespace I don't expect that to happen.