apereo / apereo/phpCAS

Issue with User Attribute Retrieval in phpCAS Versions Beyond 1.3.8

Open
#439 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
798
Forks
419
PR merge metrics
No merged PRs in 30d

Description

I wanted to bring to your attention an issue I've encountered with phpCAS versions beyond 1.3.8 regarding user attribute retrieval.

After some investigation, I found that in phpCAS version 1.3.8, I am able to successfully retrieve user attributes. However, upon upgrading to later versions, such as 1.6.1, I am unable to retrieve these attributes, despite configuring phpCAS with the same settings.

I've tried various troubleshooting steps, including reviewing the phpCAS documentation, enabling debug mode, and checking for any configuration changes between versions. However, I have not been able to resolve the issue.

It appears that there may be changes in the phpCAS logic or configuration settings in versions beyond 1.3.8 that are impacting the retrieval of user attributes. I've also noticed that rolling back to version 1.3.8 allows me to successfully retrieve user attributes again.

I wanted to bring this to your attention in the hopes that it may help improve phpCAS in future releases. If there are any specific details or logs you would like me to provide to assist with troubleshooting, please let me know.

Thank you for your attention to this matter, and I appreciate your efforts in maintaining phpCAS.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Compare user-attribute retrieval between phpCAS 1.3.8 and 1.6.1 using the same configuration, starting with the phpCAS documentation and debug output. Reproduce the regression and identify the relevant configuration or behavior change; done means attributes are retrieved in the later version or the incompatibility is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
authentication
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.