Feature Requests
Feature, docs and use-case samples requests for ServiceStack. If you can, focus on the end-user benefit / use-case, rather than the technical details so we can focus on the end-goal and free us to work on how best to achieve it. Features can also include supporting content, e.g. a starter project on how to use ServiceStack with another product (e.g. SS + SharePoint).
4 results found
-
Postman v2 format support
right now, you cannot import postman metadata exposed by SS into the latest version of Postman because its complaining about v1 schema and conversion requires an insane amount of npm garbage to be installed.
any chance of adding v2 postman metadata, or links to v1 and 2?
9 votespostman2 support is currently available as a mix in:
https://docs.servicestack.net/releases/v5.11#postman-v2-collections
Please report any issues, we’ll look at eventually replacing the existing postman support in ServiceStack in the near future.
-
Deeper SignalR Integration
I'd like to see a deeper integration between ServiceStack and SignalR. Here are a few ideas that I've so far ran into...
A Hub Authorization Attribute which implements IAuthorizeHubConnection and/or IAuthorizeHubMethodInvocation.
Some sort of JsonServiceClient integration with HubConnections. Maybe automatically associating Cookies with a new HubConnection. Plus exception handling wrappers (i.e. Like an Unauthorized exception is thrown within a SignalR exception).
Centralized documentation outlining what needs to be changed in the web.config for SignalR to co-exist with ServiceStack. Also why the UseBufferedStream property should be enabled for SignalR.
This might require a separate feature request but an updated example app…
151 votesThe way ServiceStack and SignalR will be able to integrate in future will be through .NET Core’s IApplicationBuilder pipeline which by design supports running multiple frameworks within the same App that can now share the same default route namespace.
From the v4.5.2, ServiceStack now supports running on .NET Core, please see the guide in the full release notes which shows how to register ServiceStack’s AppHost in .NET Core: http://docs.servicestack.net/releases/v4.5.2.html
SignalR for .NET Core has yet to be released but it’s expected you’ll be able to access SignalR via its dependencies registered in .NET Core’s Startup which will also be injected in your Services like normal IOC dependencies.
We’ll update this feature request again with an example showing a demo of ServiceStack + SignalR together in the same App once SignalR is available on .NET Core in 2017.
-
Built-in Active Directory Authentication suport.
I would really like to see out of the box support for IWA - Integrated Windows Authentication with Active Directory. Many in-house .Net developers for both large and small organizations write web applications that are Intranet facing, and require the use of Integrated Windows Authentication with IIS. In these environments, corporate security policy often dictates that Active Directory group membership should drive what resources a user can and cannot access.
So, Kerberos authentication often plays a big part in shipping the logged in user’s credentials via tickets from the application server to back end databases. Built-in support for a ServiceStack…163 votesA preview of AspNetWindowsAuthProvider was added in the v4.0.21 release, see:
https://github.com/ServiceStack/ServiceStack/blob/master/release-notes.md#windows-auth-provider-for-aspnet -
Management Overview Dashboard
While being able to offload to statsd/graphite/raygun/... is great, a "state of the nation" dashboard would be really handy.
This could show requests/sec, wait times, "slow" requests, auth failures, live access map, recent exceptions, known issues (e.g. can't connect to redisX/mssqlY)
231 votesServiceStack Studio is becoming our Desktop UI to inspect & manage multiple remote ServiceStack instances which now has a new User Admin Module where you can Create / Modify / Delete / Lock users, available now in the v5.10 release:
- Don't see your idea?