kubaninc / scim_rails

08 Jan, 2025

1 commit

26 Nov, 2024

3 commits

23 Nov, 2024

1 commit

22 Nov, 2024

2 commits

07 Nov, 2024

1 commit

24 Sep, 2024

1 commit

23 Sep, 2024

1 commit

21 May, 2024

1 commit

05 Jan, 2024

3 commits

30 Mar, 2023

1 commit

27 Mar, 2023

3 commits

28 Sep, 2022

1 commit

06 Jul, 2020

1 commit

02 Jul, 2020

1 commit

  • 1930828f   Fix patch endpoint archiving and case sensitivity ... Browse Dir » 
    fixes #32

After a fix shipped in #29, you could no longer de-provision a user
because when false was passed in as the value for active, it thought
there was no value for active.

fixes #33

Technically according to the specifications, the value for op is only
valid if it is one of three lower case values. However, our previous
implementation accepted a case insensitive version. Because of this, we
are adding backward compatibility for case insensitivity until we have a
chance to properly make a breaking change and only allow lower case.
    Ross Reinhardt
     

28 Jun, 2020

1 commit

17 Jun, 2020

1 commit

  • 0b5c207f   Fix exception raised when patch endpoint receives invalid request ... Browse Dir » 
    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
     

02 Jun, 2020

1 commit

29 May, 2020

1 commit

  • 7ba7da5c   Add ability to supply a callable error handler ... Browse Dir » 
    resolves lessonly/scim_rails#23

Why?
The scim engine returns a custom response to the caller in the event
that there is a 500 error in the engine. It rescues any standard error
in order to do this.

Unfortunately this means that when something is broken it does not
bubble up to the parent app's error handling system or even be printed
in the logs.

We cannot just re-raise the exception because you cannot return a
response AND raise an exception as a part of the same request.

To help, this PR will make is possible for you to supply a callable
object that take the exception as it's argument.

If no callable object is provided, we will output the exception to the
logs so that silence is not the default.

To get the old behavior of completely ignoring an exception, you could
supply an empty proc.
    Ross Reinhardt
     

19 Nov, 2019

3 commits

20 Sep, 2019

1 commit

19 Sep, 2019

2 commits

09 Apr, 2019

1 commit

05 Apr, 2019

1 commit

  • b3df225f   Remove second response content-type ... Browse Dir » 
    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
     

13 Feb, 2019

2 commits

12 Feb, 2019

1 commit

30 Jan, 2019

2 commits

29 Jan, 2019

2 commits