Skip to content
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

FEATURE_NOT_AVAILABLE when identify the signature job’s signers by contact information #366

Open
mbsalvesen opened this issue Dec 21, 2021 · 7 comments

Comments

@mbsalvesen
Copy link

Trying to use Contactinformation when creating a new Signer and getting a error message when sending/create the the job to the portalclient.

{"ErrorType:CLIENT, ErrorCode: FEATURE_NOT_AVAILABLE, ErrorMessage: Identifying a signer without personal identification number for public sector senders is not available."}

signer is created as this:
new Signer(
new ContactInformation()
{
Email = new Email(item.Email)
//Sms = new Sms(item.Telephone)
}
)
{
OnBehalfOf = OnBehalfOf.Other,
SignatureType = Digipost.Signature.Api.Client.Core.Enums.SignatureType.AdvancedSignature
});

We are aware that for public services using lookup is mandatory, and that the only instance in which this is not mandatory is if the signer is signing on behalf of someone else companies and such, in which we have to set the OnBehalfOf flag. Is it not possible to use the contact information, will we always use the personalIdentificationNumber even when signing on the behalf of someone else ? What or can we provide information about sender og signing job to be able to use the contact information, and not the personalIdentificationNumber. We were under the impression that a link could be provided for the signing job when using contact information . and that private companies could send like this ?

or is this the only way to signe on behalf of some one else:
new Signer(new PersonalIdentificationNumber("01043100118"), new Notifications(new Email("epost@example.com"))) {OnBehalfOf = OnBehalfOf.Other};

@simenstoa
Copy link
Contributor

Hi! Yes, personal identification number is mandatory for all signers of signature jobs from public sector senders. OnBehalfOf is used to support cases where the signers should not get notifications sent to their private email adresses, and should not get the signed document in their private public digital mailboxes.

or is this the only way to signe on behalf of some one else:
new Signer(new PersonalIdentificationNumber("01043100118"), new Notifications(new Email("epost@example.com"))) {OnBehalfOf = OnBehalfOf.Other};

Yes, for public sector senders, this is the way to create a signer signing on behalf of someone else.

@kurtpedersenatasikri
Copy link

@simenstoa Betyr det at en kommune eller fylkeskommune ikke vil kunne sende et dokument til signering til en privat virksomhet uten fødselsnummer?

@simenstoa
Copy link
Contributor

Ja, det stemmer dessverre. Er dette et viktig behov for dere?

@kurtpedersenatasikri
Copy link

Use caset er at en fylkeskommune ønsker å sende et dokument til signering til en kommune, er det mulig?

@simenstoa
Copy link
Contributor

Da må de nok dessverre ha personnummeret til den som skal signere i kommunen ja. Men jeg forstår godt behovet ditt, og skal ta det med tilbake til teamet. Takk for at dere melder inn slike ønsker, det er veldig nyttig for oss.

@kurtpedersenatasikri
Copy link

@simenstoa Ref dokumentasjon på denne siden: https://signering-docs.readthedocs.io/en/latest/signeringsflyt.html#signering-i-portalflyt, "On addressing a signer without a national identity number, it is the sender’s responsibility to check that the right or desired person signs the document." Betyr ikke dette at man kan sende et signeringsoppdrag uten fødselsnummer?

@simenstoa
Copy link
Contributor

Hei, og beklager sent svar. Det du refererer til gjelder for øyeblikket bare for private avsendere. Vi har meldt fra om ønske til Digdir, og notert det selv.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants