GluuFederation / GluuFederation/oxAuth

Security-related question about a possible exposed credential

Open
#1,930 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
425
Forks
145
PR merge metrics
No merged PRs in 30d

Description

Hello,

My name is Emma, I am conducting an academic study on possible credential exposure in public GitHub repositories.

While analyzing this repository, I found a string that may represent a credential. I'm including the code snippet below containing possible leakage. To avoid exposing sensitive information publicly, I marked the sensitive information.

Could you please help clarify whether the detected string is:
1. a real credential, or
2. a placeholder / example value?

Thank you for your time.

---

**Code snippet (sensitive values masked):**

```
*/
public class KeyGenerator {

private static final String SIGNING_KEYS = "sig_keys";
private static final String ENCRYPTION_KEYS = "enc_keys";
private static final String KEY_STORE_FILE = "keystore";
private static final String KEY_STORE_PASSWORD = "keypasswd";
private static final String DN_NAME = "dnname";
private static final String OXELEVEN_ACCESS_TOKEN = "at";
private static final String OXELEVEN_GENERATE_KEY_ENDPOINT = "ox11";
private static final String EXPIRATION = "expiration";
private static final String EXPIRATION_HOURS = "expiration_hours";
private static final String KEY_LENGTH = "key_length";
```

Thank you in advance for your time - I really appreciate it!

Sincerely,
Emma

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the KeyGenerator class and reviewing the constants shown in the issue, especially the key-store and access-token entries. Determine whether the values are placeholders or exposed credentials, then document the finding and any required remediation; no test or target file is identified in the report.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.