Skip to content

fix: a workaround prism did since the master key should not be handled #201

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 28, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -118,7 +118,10 @@ extension PolluxImpl {
return false
}),
case let CredentialOperationsOptions.exportableKeys(exportableKeys) = exportableKeyOption,
let exportableFirstKey = exportableKeys.filter({ $0.jwk.crv?.lowercased() == "secp256k1" }).first
let exportableFirstKey = exportableKeys.filter({
$0.jwk.crv?.lowercased() == "secp256k1"
&& !($0.jwk.kid?.contains("#master") ?? true) // TODO: This is a hardcoded fix, since prism DID doesnt not recognize master key
}).first
else {
throw PolluxError.requiresExportableKeyForOperation(operation: "Create Credential Request")
}