17 Jun, 2020

1 commit

  • fixes lessonly/scim_rails#29
    
    The patch endpoint isn't fully scim compliant yet and only allows for
    specific operations. When we received a specific format of request that
    wasn't valid, it was raising an exception instead of returning the
    expected 422 response.
    
    Add extra validation to prevent this situation when receiving an
    unexpected body for a patch request.
    Ross Reinhardt
     

11 Dec, 2019

1 commit


05 Dec, 2019

1 commit


19 Nov, 2019

3 commits


18 Oct, 2019

2 commits


02 Oct, 2019

1 commit


30 Sep, 2019

1 commit


20 Sep, 2019

1 commit


19 Sep, 2019

1 commit


09 Apr, 2019

1 commit


05 Apr, 2019

1 commit

  • See https://github.com/lessonly/scim_rails/pull/9#issuecomment-480398815
    for context. Having two content-type values for a response does not
    make sense. And in fact, Okta's SCIM API reference says we should use
    the application/scim+json response type.
    
    This commit changes our uses of two content-type values to the one
    that it should be.
    Aaron Milam
     

04 Apr, 2019

1 commit


13 Feb, 2019

1 commit


12 Feb, 2019

2 commits


30 Jan, 2019

3 commits


17 Jan, 2019

1 commit


14 Jan, 2019

1 commit


20 Dec, 2018

1 commit


19 Dec, 2018

3 commits


18 Dec, 2018

1 commit


11 Dec, 2018

3 commits