Is there a OWIN middleware that can work with a standard .NET 4.6.2 (not Core) framework to valide tokens coming from IdentityServer4.
Something like
https://github.com/IdentityServer/IdentityServer4.AccessTokenValidation
A bug has solved and now by upgrading IdentityServer3.Accesstokenvalidation to "v2.13.0" you can work with tokens come from Idsv4.
for more detail:
https://github.com/IdentityServer/IdentityServer3.AccessTokenValidation/issues/124
Even though the project README.md says OWIN Middleware to validate access tokens from IdentityServer v3. It should in theory still work with IDS4 tokens:
https://github.com/IdentityServer/IdentityServer3.AccessTokenValidation
Related
Is there some out of the box plugin for SAML2 auth or I would have to build mine from scratch?
If there's none, which library would you suggest, earlier I tried Kentor and I like how it's done, too bad I couldn't find their version of ServiceStack auth plugin.
Have a look here.
There's a collection of plug-ins.
Don't roll your own!
I am working on asp.net core webapp hosted on azure and I want to write my Elmah logs to my azure table storage .Many of the examples I looked into are using "API_KEY" and "logbucketId" but I am not sure what they are.
For instance as per elmah docs here https://docs.elmah.io/logging-to-elmah-io-from-aspnet-core/
app.UseElmahIo(
"API_KEY",
new Guid("LOG_ID"),
After installing nuget package, I don't see any API_KEY or LogBucketId in my appsettings.json file.
Where I can find my API_KEY and LogBucket_Id ?
https://github.com/ElmahCore/ElmahCore supports .net core now.
It is not based on Modules or Handlers, but Middleware.
It works fine although still limited.
The async calls are not being used at the moment. But it is quite extensible.
ELMAH doesn't work with ASP.NET Core, since ASP.NET Core doesn't work with HttpModules and HttpHandlers (ELMAH stands for Error Logging Modules And Handlers). ASP.NET Core does include a new (pre-release) diagnostic tool called ELM (Error Logging Middleware - creative, right?). You can find its source and samples here:
https://github.com/aspnet/Diagnostics/tree/release/1.1/src/Microsoft.AspNetCore.Diagnostics.Elm
Another option similar to ELMAH (and ELM) but with more capabilities is Glimpse:
http://getglimpse.com/
I realize neither of these directly answers your question but hopefully you'll find one or both of these alternative tools useful.
You can check ELMAH port to Net.Core version
https://github.com/ElmahCore/ElmahCore
Make sure it is matching your expectation before you use it.
Note: This new extension is in development and doesn't support all Elmah features.
ELMAH doesn't support ASP.NET Core. The documentation you are linking to is from elmah.io. While they have similar names and elmah.io uses ELMAH for some of its integrations, they don't share code or documentation.
Is Asp.net 5 pre-build with OWIN(Katana) package?
We don't need to add the Microsoft.Owin dll package into Asp.net 5.
Am I right?
If we want to use OWIN then what's lacking in Asp.Net 5?
Thanks,
Chandru
Edit:
According to this The new asp.net pipeline supports OWIN through OWIN adapter, here is an example of that, more info on how OWIN fit in with asp.net 5 here.
No, if you want to use it you need to add it to the pipeline through Startup.cs
No, You need to add the Microsoft.AspNet.Owin to use it.
You need to add middleware request pipeline, use Microsoft.AspNet.Owin
No, Asp.Net 5 is not built on OWIN (there is no IDictionary<string, object> environment), but it does use similar concepts and there is an interop package available. See https://github.com/aspnet/HttpAbstractions/tree/dev/src/Microsoft.AspNet.Owin, https://github.com/aspnet/Entropy/tree/dev/samples/Owin.IAppBuilderBridge, http://blogs.msdn.com/b/webdev/archive/2014/11/14/katana-asp-net-5-and-bridging-the-gap.aspx
I'm currently trying to host a REST webservice on ios/android using Xamarin and monotouch/monodroid. I already successfully have a basic webserver running using HttpListener, but now I would like to host a complete webservice using ServiceStack.
monotouch/monodroid have very limited web hosting capabilities (HttpListener is basically the only way), but ServiceStack can in theory accomodate with that.
It seems to be possible as I found someone who did it: http://www.servicestack.net/mythz_blog/?p=417
The problem is that project does not work anymore on the last monotouch version, and ServiceStack seems to have removed server hosting capabilites in the monotouch/monodroid latest builds...
Xamarin have a fork of ServiceStack (https://github.com/xamarin/ServiceStack) which seems to have hosting capabilities, but the monotouch specific service hosting build does not compile, and the fork seems outdated.
Has anyone succeeded in making the ServiceStack hosting capabilities work on monotouch/monodroid? Or do you have an idea on how to make it work?
You might try this tutorial for self-hosting ServiceStack.
It looks like it will use HttpListener under the hood, but I don't know if the AppHostHttpListenerBase class will compile for MonoTouch/Mono for Android or not.
Ok so after some research, the project to allow ServiceStack self-hosting has been dropped. It had a better luck with the (old) Xamarin version (https://github.com/xamarin/ServiceStack) and could compile it and make it work somehow.
Since I need to be in sync with the latest ServiceStack version, I guess that I have no other choice than to roll my own adaptation, using the old Xamarin branch as a starting point.
Is it possible to run servicestack's built-in clients on the .net client profile framework?
When i change the target framework property in the project settings to ".Net Framework Client Profile" and try to compile i get the following message: the namespace ServiceClient does not exist in the namespace servicestack.
We use servicestack services to send exception reports. We use the JsonServiceClient and feel really comfortable with it. We could change the target framework - but then we have to check all installations for the availability of the full .net framework.
Any idea how to solve this?
Thanks.
From the package contents of the latest ServiceStack.Common package there seems to be no -client version included (See Common Framework and Profile Targeting Examples under NuGet - Creating and Publishing a Package).
You should either change the target framework the full profile or pull the code from ServiceStack's GitHub Repo and try to build it for client profile yourself. The downside of this is that you will loose Nuget's awesome update features...
You could off course file an issue at GitHub for the guys maintaining ServiceStack to add a client profile version of the framework, but I guess that there's a good reason for why it's not there already.