162 results found

1. Add ServiceStack + SharePoint example

   Create a starter template showing how to use ServiceStack + SharePoint together.

   31 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Unions implementation for ORM Lite

   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);

   28 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Better request and exception logging

   As it exists now, request logging only logs valid requests.
   Request Logging:

   It does not log the request if the request is denied for Endpoint Restriction.
   It does not log the request if the request is denied because a route could not be matched (say a parameter was missing, etc).
   It does not log valid requests that are 'in process' - ones that request has been received, but response not sent yet.

   Essentially I would like to see every request sent to the service to be logged in some fashion.

   As far as exceptions go, you have some pretty nice logging right now. However, it does not log anything about the request. I would like to see where the request came from, url, get/put/post/method, contents of what was posted, etc. Essentially everything I need. As it is now, I have to use fiddler debugger or something to get this done. Would be nice if the logging output the information.

   As it exists now, request logging only logs valid requests.
   Request Logging:

   It does not log the request if the request is denied for Endpoint Restriction.
   It does not log the request if the request is denied because a route could not be matched (say a parameter was missing, etc).
   It does not log valid requests that are 'in process' - ones that request has been received, but response not sent yet.

   Essentially I would like to see every request sent to the service to be logged in some fashion.

   As far as exceptions go, you have some pretty nice… more

   28 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. ExcludePropertyReferences for Data Contracts

   Currently ExcludePropertyReferences is expecting DeclaringTypeName.DataContractName. Its more helpful if the type is fully qualified.

   for example ; from below Json if we want to exclude :{"Officeaddress.houseaddress.city"}; .

   Json:
   //----------------------------------------------------------------------------
   {"id":"eb26f100-3758-4a19-806b-cd5af44f88a4","data":{"lname":"Talluri","firstname":"RamaNaresh","city":"Atlanta"},"collections":{"houseaddress":[{"id":"126e057d-e91b-42ec-b40d-bdba9c831d64","data":{"city":"CAToronto"}}],"officeaddress":[{"id":"5ff48bd4-bfe2-4721-adf1-3f5cd3b5c736","data":{"city":"USAlpharetta"},"collections":{"houseaddress":[{"id":"aad21efc-2768-4518-a505-71dc8b82ad40","data":{"city":"CA_Downtown"}}]}}]}}
   //----------------------------------------------------------------------------
   Model :
   //----------------------------------------------------------------------------
   [DataContract]
   public class AddressModel : BaseModel
   {
   [DataMember(Name = "id")]
   public System.Guid Id
   {
   get;
   set;
   }

       [DataMember(Name = "data")]
       public virtual BaseAddress Data
       {
           get;
           set;
       }
   
       [DataMember(Name = "collections")]
       public virtual AddressCollection Collections
       {
           get;
           set;
       }
   }
   
   [DataContract]
   public class BaseAddress
   {
   
       [DataMember(Name = "lname")]
       public string LastName
       {
           get;
           set;
       }
       [DataMember(Name = "firstname")]
       public string FirstName
       {
           get;
           set;
       }
       [DataMember(Name = "city")]
       public string City
       {
           get;
           set;
       }
   }
   
   
   [DataContract()]
   public class AddressCollection
   {
   
       [DataMember(Name = "houseaddress")]
       public virtual List<HAdddress> HAdddress{get; set;}
   
   
       [DataMember(Name = "officeaddress")]
       public virtual List<OAdddress> OAdddress { get; set; }
   
   }
   
   
   [DataContract]
   public class HAdddress
   {
       [DataMember(Name = "id")]
       public System.Guid Id
       {
           get;
           set;
       }
   
       [DataMember(Name = "data")]
       public virtual HAddressData Data
       {
           get;
           set;
       }
   }
   
   [DataContract]
   public class OAdddress
   {
       [DataMember(Name = "id")]
       public System.Guid Id
       {
           get;
           set;
       }
   
       [DataMember(Name = "data")]
       public virtual OAddressData Data
       {
           get;
           set;
       }
   
       [DataMember(Name = "collections")]
       public virtual SeAdddress Collection { get; set; }
   }
   
   [DataContract]
   public class HAddressData
   {
       [DataMember(Name = "city")]
       public string City { get; set; }
   }
   
   [DataContract]
   public class OAddressData
   {
   
       [DataMember(Name = "city")]
       public string City { get; set; }
    }
   
   [DataContract]
   public class SeAdddress
   {
       [DataMember(Name = "houseaddress")]
       public virtual List<HAdddress> SECAdddress { get; set; }
   }
   
   [DataContract]
   public class SeAdddress2
   {
   [DataMember(Name = "id")]
       public System.Guid Id
       {
           get;
           set;
       }
   
       [DataMember(Name = "data")]
       public virtual BaseAddress Data
       {
           get;
           set;
       }
   }
   

   [DataContract]
   public class BaseModel
   {
   }

   //-------------------------------------------------------------------------
   object to serialize
   //-------------------------------------------------------------------------
   var aModel = new AddressModel
   {
   Id = Guid.NewGuid(),
   Data = new BaseAddress() {FirstName = "RamaNaresh", LastName = "Talluri", City = "Atlanta"},
   Collections = new AddressCollection()
   {
   HAdddress = new List<HAdddress>()
   {
   new HAdddress() {Id = Guid.NewGuid(), Data = new HAddressData() {City = "CAToronto"}}
   },
   OAdddress = new List<OAdddress>()
   {
   new OAdddress()
   {
   Id = Guid.NewGuid(),
   Data = new OAddressData() {City = "USAlpharetta"},
   Collection = new SeAdddress()
   {
   SECAdddress =
   new List<HAdddress>()
   {
   new HAdddress()
   {
   Id = Guid.NewGuid(),
   Data = new HAddressData() {City = "CA_Downtown"}
   }
   }
   }
   }
   }
   }
   };

   jsScope.ExcludePropertyReferences= new []{"Officeaddress.houseaddress.city"};

   Thanks

   Currently ExcludePropertyReferences is expecting DeclaringTypeName.DataContractName. Its more helpful if the type is fully qualified.

   for example ; from below Json if we want to exclude :{"Officeaddress.houseaddress.city"}; .

   Json:
   //----------------------------------------------------------------------------
   {"id":"eb26f100-3758-4a19-806b-cd5af44f88a4","data":{"lname":"Talluri","firstname":"RamaNaresh","city":"Atlanta"},"collections":{"houseaddress":[{"id":"126e057d-e91b-42ec-b40d-bdba9c831d64","data":{"city":"CAToronto"}}],"officeaddress":[{"id":"5ff48bd4-bfe2-4721-adf1-3f5cd3b5c736","data":{"city":"USAlpharetta"},"collections":{"houseaddress":[{"id":"aad21efc-2768-4518-a505-71dc8b82ad40","data":{"city":"CA_Downtown"}}]}}]}}
   //----------------------------------------------------------------------------
   Model :
   //----------------------------------------------------------------------------
   [DataContract]
   public class AddressModel : BaseModel
   {
   [DataMember(Name = "id")]
   public System.Guid Id
   {
   get;
   set;
   }

       [DataMember(Name = "data")]
       public virtual BaseAddress Data
       {
           get;
           set;
       }
   
       [DataMember(Name = "collections")]
       public virtual AddressCollection Collections
       {
           get;
           set;
       }
   }
   
   [DataContract]
   public class BaseAddress
   {
   
       [DataMember(Name = "lname")]
       public string LastName
       {
           get;
           set;
       }
       [DataMember(Name = "firstname")]
       public string FirstName
       {
           get;
           set;

   … more
   27 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Add an LDAP Authentication Provider

   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.

   24 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Two Factor Authentication Feature

   Two Factor Authentication is a pretty standard thing nowadays, it even comes baked into the typical ASP.NET Core Identity system. It would be nice if Service Stack had this feature as well. We are working on porting a legacy application from ASP.NET to ServiceStack and this is a requirement for government applications (some form of TFA).

   23 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Azure DocumentDB caching provider

   Support Azure DocumentDB as an available caching provider for Azure hosts.

   23 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Add persistence support for Couchbase

   This shouldn't be too hard considering you seem to already support memcached..?

   20 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Add Emailing functionality to Verify Account, Request Password Reset

   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.

   19 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. AutoQuery Azure DocumentDB Data Source

    Azure DocumentDB should be added among existing AutoQuery data source.

    19 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. support F# data type for serialization and deserialization

    This is specially for option type and discriminated unions. Currently it is not supported by Servicestack.Text. It would be great to have support for that.

    For

    type City = Abad | Pune

    [<CLIMutableAttribute>]
    type Person = {
    FirstName:string
    LastName: string option
    City : City
    }

    let p1 = {FirstName = "Foo"; LastName = Some "Bar"; City = Pune}

    let jss = new JsonStringSerializer()
    let p1Str = jss.SerializeToString(p1)

    It is serializing
    "{"FirstName":"Foo","LastName":{"Value":"Bar"},"City":{"Tag":1,"IsAbad":false,"IsPune":true}}"

    Where is should be
    "{"FirstName":"Foo","LastName":"Bar","City":"Pune"}"

    For reference https://github.com/Microsoft/fsharplu/wiki/fsharplu.json is library by MSR.

    It would be great to have this feature so DTO can be written in F# types. Currently we have to translate to C# like object so it can be serialize properly.

    This is specially for option type and discriminated unions. Currently it is not supported by Servicestack.Text. It would be great to have support for that.

    For

    type City = Abad | Pune

    [<CLIMutableAttribute>]
    type Person = {
    FirstName:string
    LastName: string option
    City : City
    }

    let p1 = {FirstName = "Foo"; LastName = Some "Bar"; City = Pune}

    let jss = new JsonStringSerializer()
    let p1Str = jss.SerializeToString(p1)

    It is serializing
    "{"FirstName":"Foo","LastName":{"Value":"Bar"},"City":{"Tag":1,"IsAbad":false,"IsPune":true}}"

    Where is should be
    "{"FirstName":"Foo","LastName":"Bar","City":"Pune"}"

    For reference https://github.com/Microsoft/fsharplu/wiki/fsharplu.json is library by MSR.

    It would be great to have this feature so DTO can be written in F# types. Currently… more

    17 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Add Navigation Properties To POCOs

    Entity Framework currently has navigation properties for foreign keys to other tables. Having this feature in OrmLite would be absolutely amazing.

    16 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Support for Redis Streams (5.0+)

    Implement support for Redis 5.0+ Streams, as described here:

    https://redis.io/topics/streams-intro

    16 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Response field filtering

    As per this example: http://www.vinaysahni.com/best-practices-for-a-pragmatic-restful-api#limiting-fields

    It would be useful to be able to restrict the returned fields provided by the response.

    Using a dot notation we could filter any nested properties as well. e.g.

    GET /customers/fields=id,name,address,address.postcode,address.line1

    16 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Add Metrics.NET Adapter

    Add support for Metrics.NET: https://github.com/etishor/Metrics.NET

    They already have adapters for Nancy & Owin: https://github.com/etishor/Metrics.NET/tree/master/Src/Adapters

    I've also posted a question wheter the maintainer of Metrics.NET has any plan in doing it for ServiceStack in his repo: https://github.com/etishor/Metrics.NET/issues/101

    16 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Enhance ServiceStack Razor page lookup options

    I have a custom basic CMS I put together (work in progress) for some of my clients that allows developers to build CMS plugins that auto-install on application startup. The plugins can deploy both content pages and view pages (and use ServiceStack plugins and CMS plugin interfaces to configure, and add capabilities to the CMS at startup), similar to how NopCommerce and Orchard work.

    Currently, I have to rely on view pages to be unique, but I would like to be able to modify the lookup algorithm to take advantage of paths to the razor/markdown pages in the Views folder, so that page name uniqueness isn't required (each plugin right now that wants to take advantage of View pages has to preface their view right now in their Views directory with a plugin prefix, i.e.: blog-index.cshtml, events-index.cshtml, instead of Views/<plugin_folder_name>/index.cshtml).

    Content pages don't have this issue...

    Maybe in it's most basic form enhance with another attribute [DefaultViewPath(~/blog)], or [DefaultViewPath(<regex>)] that we can tag our DTOs or services with (or enhance the existing DefaultView attribute) ... Better maybe, an interface that can be implemented and registered that would control how the view pages (name and path) are registered in the lookup dictionary, and also how they are queried to determine the one to use at runtime.

    This ability to have my own implementation would be beneficial. I have some theming in the CMS built-in for example, so that the path could look like this Views/Themes/<theme_name>/<plugin_folder_name>/index.cshtml. If a path doesn't exist, the child theme algorithm kicks in to resolve the proper path, until it reaches the root default theme path (similar to Wordpress), where every page always has a version of itself.

    Right now I have various workarounds that make all this work, but I've had to re-write some classes in ways that wouldn't be beneficial to the community, too custom for my scenario ...

    I will also probably be looking into leveraging paths in special localization cases, still brain-storming that.

    Just an idea, probably not gonna top the list, but thought I would throw it in. If nothing is done, I will make do. I'm very curious to see if anyone is leveraging the awesome ServiceStack Razor code base and running into issues like this.

    I have a custom basic CMS I put together (work in progress) for some of my clients that allows developers to build CMS plugins that auto-install on application startup. The plugins can deploy both content pages and view pages (and use ServiceStack plugins and CMS plugin interfaces to configure, and add capabilities to the CMS at startup), similar to how NopCommerce and Orchard work.

    Currently, I have to rely on view pages to be unique, but I would like to be able to modify the lookup algorithm to take advantage of paths to the razor/markdown pages in the Views folder,… more

    15 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Include XML documentation files in the NuGet releases

    It seems no XML documentation is shipped with NuGet packages. This makes discovery hard, for example with Intellisense in Visual Studio, and is a shame given that the documentation is already written.

    http://stackoverflow.com/questions/19719607/how-can-i-get-servicestacks-xml-documentation-to-show-in-visual-studio

    13 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Backend Hosting Environment

    When starting a new project one always has to build a backend environment. This includes managing users, user groups, user password changes, etc. etc. This requires a backend database and an admin front-end.

    Currently, we use the ASPNETZERO framework for this purpose. https://aspnetzero.com/ But the support, documentation, and performance leave a lot of room for improvement.

    We're looking to move away from ASPNETZERO as soon as we can find a replacement. Currently, their pricing starts at $1500 a year for updates and support. Something that I would gladly pay, except the documentation and support they provide is horrible.

    It would also be a showcase for all of the great capabilities of ServiceStack.

    When starting a new project one always has to build a backend environment. This includes managing users, user groups, user password changes, etc. etc. This requires a backend database and an admin front-end.

    Currently, we use the ASPNETZERO framework for this purpose. https://aspnetzero.com/ But the support, documentation, and performance leave a lot of room for improvement.

    We're looking to move away from ASPNETZERO as soon as we can find a replacement. Currently, their pricing starts at $1500 a year for updates and support. Something that I would gladly pay, except the documentation and support they provide is horrible.

    It would… more

    13 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    7 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Allow customization of ModelDefinition in ORM Lite

    I need to be able to customize the ModelDefinition after it is generated by ORM Lite. I propose adding a method to IOrmLiteDialectProvider named CustomizeModelDefinition(ModelDefinition modelDef). In the base dialect providers, there are multiple methods used to create ModelDefinitions. I propose that all of those calls be routed through one method in OrmLiteConfig.GetModelMetadata(this Type modelType). In that method, after the model is created, it would invoke DialectProvider.CustomizeModelDefinition(modelDef). I downloaded and implemented this and tested it. It didn't take long and worked well. I would be happy to share the code.

    12 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    4 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. okta

    Add OKTA as a built-in authentication provider.

    12 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close