At the moment, the *OAuth2 Providers for ServiceStack* library does not support .net core, as explained by mythz in this StackOverflow answer:

> ServiceStack's OAuth2 depends on DotNetOpenAuth which unfortunately doesn't support .NET Core so there's currently no support for OAuth2 - https://stackoverflow.com/a/42344183/969613

Google Authentication is a feature requirement on my current project, so this one thing is preventing us from moving to .net core, support for this would be great.

I understand if this is changed it may break projects based on Typescript < 2.4. I propose a new flag or option to serialize enum strings as enum strings instead of string literals. This would minimally allow us to get access to the list of strings available for an enum which is not readily available with a string Literal.

Instead of this:

export type MessagePriority = "Normal" | "Low" | "High";

It would be:

export enum MessagePriority{
Normal = "Normal",
Low = "Low",
High = "High"
}

I was just reading about the Redis Labs new RediSearch product for use in implementing a search engine in Redis. I saw in the RediSearch product page that StackExchange has a C# client for this product. Do you plan to implement RediSearch client in ServiceStack.Redis? I prefer ServiceStack modules to StackExchange.

If this is your roadmap, can you project delivery of such a client?

Keep up the good work! Thanks!

By default the metadata page could group the operations by the service they are in.
All user operations under UserService.
Order operations under OrderService.
etc.

In order to improve security it would be beneficial to change cookie names from const to a configurable option. It would help mask the presence of service stack and improve security in accordance with OWASP recommendations - https://www.owasp.org/index.php/Session_Management_Cheat_Sheet#Session_ID_Name_Fingerprinting

Please implement Brotli compression support for request and response payloads. (-:

There exists a few C# libraries, like this one: https://github.com/XieJJ99/brotli.net

Add a MQ Server for MSMQ that implements ServiceStack's Messaging API: http://docs.servicestack.net/messaging

The actual idea

It would be a good idea for users when using Service Stack Authentication to have functionality like Asp.net Identity to Verify their account, reset their password.

The API request logger logs all fields and there is now way to disable any of them. Specifically, logging the users cookie each time takes up a huge amount of space and also makes the display difficult to use. Please add a config option to allow control over which fields get logged.

Add OKTA as a built-in authentication provider.

Hi

In my application user can define multiple filters for specific type. I would like to somehow combine these queries in single one.

SqlExpression<Notice> query1 = Db.From<Notice>(s=>s.param1 == 2);
// ...queries are more complicated but result type is same
SqlExpression<Notice> query2 = Db.From<Notice>(s=>s.param1 == 3 && s.param2 == 3);

SqlExpression<Notice> unionAll = query1.UnionAll(query2);
var result = Db.Select(unionAll);

Provide a package that allows hosting ServiceStack services (specifically web services and web sockets) in a UWP environment. The primary use-case for this is to allow ServiceStack services to run on an IoT device using UWP IoT Core.

I believe we can retrieve specific versions of a file via the versionId querystring using VirtualFiles.... however VirtualFiles.WriteFile returns null so we cannot retrieve the x-amz-version-id header. It would be nice if the headers were in the response of VirtualFiles.WriteFile so we could retrieve that.

To MsgPack was really comfortable as JSON, you must add the possibility of setting "Map" mode. This will give more compatibility when migrating from one version to another, when service is updated, but clients have not yet had time.

We have message-level encryption and the corresponding .Net client library to use it. But I'd love to be able to call encrypted services from JavaScript. Ideally add to ss-utils.js, or because the encryption can get bulky, into a new ss-encrypt-utils.js.

With .NET Core not initially having support for Windows Authentication using the System.Directory assemblies, I would like to request the addition of a new LDAP Authentication Provider based on the Novell.Directory.Ldap.NETStandard (https://github.com/dsbenghe/Novell.Directory.Ldap.NETStandard) project. This will allow developers to update to the latest ServiceStack while still providing a way to authenticate and authorize against a legacy/non-Azure Active Directory.

Azure DocumentDB should be added among existing AutoQuery data source.

when add a service stack reference we can use include types and exclude types.

could you add include / exclude by route.

so, we can configure reference like this way.

//include route "/mobile%"
or
//include route "%mobile%"