Skip to content
This repository has been archived by the owner on Jul 31, 2024. It is now read-only.

Add API to interaction service to return error to client #2766

Closed
brockallen opened this issue Oct 31, 2018 · 5 comments
Closed

Add API to interaction service to return error to client #2766

brockallen opened this issue Oct 31, 2018 · 5 comments
Assignees
@brockallen
Labels
enhancement pinned ready

Comments

@brockallen
Copy link
Member

Now there's a APi to return access_denied, but might be nice to have an API to trigger login_required or some other similar errors back to the client.
@brockallen brockallen added this to the 2.4 milestone Oct 31, 2018
@brockallen brockallen self-assigned this Oct 31, 2018
@brockallen brockallen modified the milestones: 2.5, Future Apr 29, 2019
@Randy808
Copy link

In which scenarios should 'login_required' be returned?

@brockallen brockallen modified the milestones: Future, 4.0 Dec 10, 2019
@stale
Copy link

stale bot commented Jan 10, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jan 10, 2020
@stale stale bot removed the wontfix label Jan 10, 2020
brockallen added a commit that referenced this issue Mar 24, 2020
@brockallen
Add API to interaction service to return error to client #2766
ee60e9d
@brockallen brockallen mentioned this issue Mar 24, 2020
Merged
@brockallen
Copy link
Member Author

PR submitted.

leastprivilege pushed a commit that referenced this issue Mar 30, 2020
@brockallen
Add API to interaction service to return error to client (#4204)
ad12f11 
* Add API to interaction service to return error to client #2766

* update hosts for ef and aspid projects
@brockallen brockallen removed this from the 4.0 milestone Mar 30, 2020
@brockallen
Copy link
Member Author

PR merged

@lock
Copy link

lock bot commented May 5, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators May 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@brockallen brockallen

Labels
enhancement pinned ready
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@brockallen @leastprivilege @Randy808