servicestack

I'm having some dramas making a call against a ServiceStack REST service which I've secured with an out of the box IdentityServer STS. I'm making an AJAX call against the REST endpoint, and I'm not sure how one might setup a logon procedure to get a security token to pass. The REST endpoint is on a different domain than the website making the call. The info that I've found so far all seems to revolve around the procedure where the client makes a call to the secured resource gets a 302 redirect to the identityserver logon page, then after successful authentication gets a 302 redirect to either

I have a .NET application built with Mono, that I've bundled into a native (Linux) executable using mkbundle . This is so that end users don't need to mess around and install Mono themselves. The application uses ServiceStack, which under the hood uses HttpListener . I need the web services to be exposed over an SSL-enabled HTTP endpoint. Normally, you would run something like httpcfg -add -port 1234 -p12 MyCert.pfx -pwd "MyPass" during configuration (all this really does is copy the certificate to a specific path), and HttpListener would automatically bind the certificate to the port. So

There are existing tools for auto generating API documentation - most of the weren't designed for REST services. For all of you who have created REST services using ServiceStack - how did you write the docs ? Manual / semi-auto / fully auto-gen ? I'm even considering auto gen a customized WADL and connecting it to something like apigee Console To Go (oh and RESTafaries- please spare the 'REST api should be auto discoverable and self-explained' mantra...I really want nice looking docs for my users). Documenting an API through XHTML might provide better results than formatting DTO's. Look at

I want to create the table with custom name but I cannot find the sample code. I notice the only way to create table is by generic type like db.CreateTable(). May I know if there is a way to create the table name dynamically instead of using Alias? The reason is because sometime we want to store the same object type into different tables like 2015_january_activity, 2015_february_activity. Apart from this, the db.Insert also very limited to object type. Is there anyway to insert by passing in the table name? I think these features are very important as it exists in NoSQL solution for long and

I've been looking at ServiceStack and I'm trying to understand how to use BasicAuthentication on a service with an existing database. I would like to generate a public key (username) and secret key (password) and put that in an existing user record. The user would then pass that to the ServiceStack endpoint along with their request. What do I need to implement in the ServiceStack stack to get this working? I have looked at both IUserAuthRepository and CredentialsAuthProvider base class and it looks like I should just implement IUserAuthRepository on top of my existing database tables. I am

I have not tried this yet, but I would like each module (Silverlight) to register its own routes, rather then adding it in application start. Can routes be added to AppHost after application start, or do they all have to be immediatelly registered during Configure step? I am thinking to scan all assemblies at the startup and provide AppHost with all assemblies that implement service stack services, but let each module add its own routes (have not figured out yet exact mechanism. Before I go down this route, need to know if it is possible to add routes after the Configure step. All

I need to service localized data. All response Dtos which are localized share the same properties. I.e. I defined an interface ( ILocalizedDto ) to mark those Dtos. On the request side, there is a ILocalizedRequest for requests which demand localization. Using IPlugin I already managed to implement the required feature. However I am quite sure that the implementation is not thread safe and additionally I don't know if I could use IHttpRequest.GetHashCode() as identifier for one request/response cycle. What would be the correct way to implement a ServiceStack plugin which makes use of both

I'm using ServiceStack with great results so far, except that dealing with errors is seemingly tricky. If something goes wrong during serialization of a message (because I forgot to add a default constructor to the message for example) all the client gets back is a message that the server had an internal error and a status code of 500. Adding a listener to the HttpApplication.Error event in the Global.asax doesn't work as it never gets hit. Neither does Application_Error . Not only is this insufficient for end user scenarios, it makes debugging these errors very cumbersome as the only way to