faces/FlashSecretKey and faces/ClientSideSecretKey are missing in spec
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 127
- Forks
- 59
- Avg merge
- 23h
- Merged PRs (30d)
- 7
Description
As per https://github.com/eclipse-ee4j/mojarra/issues/5552 I found out that predefined JNDI variables faces/FlashSecretKey and faces/ClientSideSecretKey are nowhere mentioned in https://jakarta.ee/specifications/faces/4.0/jakarta-faces-4.0.
I wonder if these should be mentioned in the Faces spec at all?
@tandraschko How exactly does MyFaces deal with encrypted Flash state and Client Side state across server restarts without session persistence and/or across distributed systems? The goal is of course that any encrypted Flash state and/or Client Side state needs to be decryptable after server restart and/or on a different server with same session. I scanned for these JNDI variables in MyFaces source code but I couldn't find any.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the Jakarta Faces 4.0 specification with the behavior described in Mojarra issue 5552. Investigate how MyFaces handles the two JNDI variables and encrypted Flash and client-side state across restarts or distributed servers; done means deciding whether the variables belong in the Faces spec and documenting the agreed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100