SdJwtInlineIssuanceEntry

Artifact: androidx.credentials.registry:registry-digitalcredentials-sdjwtvc

Kotlin |Java

class SdJwtInlineIssuanceEntry : InlineIssuanceEntry

kotlin.Any
↳	androidx.credentials.registry.provider.digitalcredentials.InlineIssuanceEntry
	↳	androidx.credentials.registry.digitalcredentials.sdjwt.SdJwtInlineIssuanceEntry

An entry offering the user an opportunity to add a digital credential to your holder / wallet application during the presentation moment.

This serves as a fallback or alternative to a real digital credential that can be presented. When the verifier application requests for a digital credential presentation, it is possible that the user has not officially add their corresponding digital credential(s) to their holder application yet. The SdJwtInlineIssuanceEntry allows the holder application to add the credentials on the fly and then immediately return them, allowing the request, as well as the future requests, to still succeed.

Throws
`kotlin.IllegalArgumentException`	if `id` length is greater than 64 characters
`kotlin.IllegalArgumentException`	if `supportedSdJwts` is empty

Summary

Nested types
`class SdJwtInlineIssuanceEntry.SupportedSdJwt` Configuration determining whether the `SdJwtInlineIssuanceEntry` should be offered for a presentation request

Public constructors
`SdJwtInlineIssuanceEntry( id: String, display: InlineIssuanceEntry.InlineIssuanceDisplayProperties, supportedSdJwts: Set<SdJwtInlineIssuanceEntry.SupportedSdJwt> )`

Public functions
`open operator Boolean`	`equals(other: Any?)`
`open Int`	`hashCode()`

Public properties
`Set<SdJwtInlineIssuanceEntry.SupportedSdJwt>`	`supportedSdJwts` supported SD-JWTs to offer the inline issuance flow; cannot be empty

Inherited properties

From androidx.credentials.registry.provider.digitalcredentials.InlineIssuanceEntry

`InlineIssuanceEntry.InlineIssuanceDisplayProperties`	`display` the display properties associated with the given entry
`String`	`id` the provider unique identifier of this credential entry, which can be used to identify the exact credential that the user has chosen; it is recommended that you generate this `id` with enough entropy that it cannot be guessed by a third party, e.g. through encrypting this `id` or randomizing it.

Public constructors