Skip to content

[Alpha v19.0.8] 401 API Authorization Issue When Adding a New Defined Value in the Add New Request Dialog #6794

@leahjennings

Description

@leahjennings

Description

If a connection request has an attribute of type Defined Value and you try to add a new Defined Value while creating the connection request, there's an error. The console indicates it is a 401 auth error with the v2 API endpoint /api/v2/Controls/DefinedValueEditorSaveNewValue, however I tested the ability to add additional defined values in other interfaces in Rock. Those worked just fine, and I assume they also use that endpoint, although I do not know that for certain. The endpoint correctly has RSR - Rock Administration set to allow.

Actual Behavior

There's a 401 authorization error that occurs if you try to add a new defined value to an attribute in the interface when adding a new connection request.

Expected Behavior

I would expect to be able to add a new defined value to the attribute when creating a new connection request.

Steps to Reproduce

  • On a Rock instance running at least v19, go to People > Connections
  • Click on the gear that lets you edit connection types
Image
  • Click on the Involvement type, then click Edit
  • Scroll to Request Attributes, and add a new one
  • Add a new attribute of type Defined Value (see screenshot for details)
    • the key is that you select allow adding new values
Image
  • Click Save on the dialog, then Save the Connection Type
  • Go to People > Connections
  • Click on the Connections List for the Involvement Connection Type
  • Click the + button to add a new connection request
Image
  • Scroll to the bottom and click the + button next to the Defined Value field
  • Fill in details, then click Add
Image
  • Notice the error message
Image
  • The console shows a 401 authorization error for a specific v2 API endpoint, however the security for that endpoint is correct (and works elsewhere in Rock)
Image

Issue Confirmation

  • Perform a search on the Github Issues to see if your bug is already reported.
  • Reproduced the problem on a fresh install or on the demo site.

Rock Version

Rock McKinley 20.0 (20.0.1)

Client Culture Setting

en-US

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions