forked from openiddict/openiddict-core
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathOpenIddictResources.resx
3052 lines (3041 loc) · 173 KB
/
OpenIddictResources.resx
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version="1.0" encoding="utf-8"?>
<root>
<!--
Microsoft ResX Schema
Version 2.0
The primary goals of this format is to allow a simple XML format
that is mostly human readable. The generation and parsing of the
various data types are done through the TypeConverter classes
associated with the data types.
Example:
... ado.net/XML headers & schema ...
<resheader name="resmimetype">text/microsoft-resx</resheader>
<resheader name="version">2.0</resheader>
<resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>
<resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>
<data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>
<data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>
<data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">
<value>[base64 mime encoded serialized .NET Framework object]</value>
</data>
<data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">
<value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>
<comment>This is a comment</comment>
</data>
There are any number of "resheader" rows that contain simple
name/value pairs.
Each data row contains a name, and value. The row also contains a
type or mimetype. Type corresponds to a .NET class that support
text/value conversion through the TypeConverter architecture.
Classes that don't support this are serialized and stored with the
mimetype set.
The mimetype is used for serialized objects, and tells the
ResXResourceReader how to depersist the object. This is currently not
extensible. For a given mimetype the value must be set accordingly:
Note - application/x-microsoft.net.object.binary.base64 is the format
that the ResXResourceWriter will generate, however the reader can
read any of the formats listed below.
mimetype: application/x-microsoft.net.object.binary.base64
value : The object must be serialized with
: System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
: and then encoded with base64 encoding.
mimetype: application/x-microsoft.net.object.soap.base64
value : The object must be serialized with
: System.Runtime.Serialization.Formatters.Soap.SoapFormatter
: and then encoded with base64 encoding.
mimetype: application/x-microsoft.net.object.bytearray.base64
value : The object must be serialized into a byte array
: using a System.ComponentModel.TypeConverter
: and then encoded with base64 encoding.
-->
<xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
<xsd:import namespace="http://www.w3.org/XML/1998/namespace" />
<xsd:element name="root" msdata:IsDataSet="true">
<xsd:complexType>
<xsd:choice maxOccurs="unbounded">
<xsd:element name="metadata">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="value" type="xsd:string" minOccurs="0" />
</xsd:sequence>
<xsd:attribute name="name" use="required" type="xsd:string" />
<xsd:attribute name="type" type="xsd:string" />
<xsd:attribute name="mimetype" type="xsd:string" />
<xsd:attribute ref="xml:space" />
</xsd:complexType>
</xsd:element>
<xsd:element name="assembly">
<xsd:complexType>
<xsd:attribute name="alias" type="xsd:string" />
<xsd:attribute name="name" type="xsd:string" />
</xsd:complexType>
</xsd:element>
<xsd:element name="data">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
<xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />
</xsd:sequence>
<xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />
<xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />
<xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />
<xsd:attribute ref="xml:space" />
</xsd:complexType>
</xsd:element>
<xsd:element name="resheader">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
</xsd:sequence>
<xsd:attribute name="name" type="xsd:string" use="required" />
</xsd:complexType>
</xsd:element>
</xsd:choice>
</xsd:complexType>
</xsd:element>
</xsd:schema>
<resheader name="resmimetype">
<value>text/microsoft-resx</value>
</resheader>
<resheader name="version">
<value>2.0</value>
</resheader>
<resheader name="reader">
<value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
</resheader>
<resheader name="writer">
<value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
</resheader>
<data name="ID0002" xml:space="preserve">
<value>An identity cannot be extracted from this request.
This generally indicates that the OpenIddict server stack was asked to authenticate a request for an endpoint it doesn't manage.
To validate tokens received by custom API endpoints, the OpenIddict validation handler (e.g OpenIddictValidationAspNetCoreDefaults.AuthenticationScheme or OpenIddictValidationOwinDefaults.AuthenticationType) must be used instead.</value>
</data>
<data name="ID0003" xml:space="preserve">
<value>The token type is not supported.</value>
</data>
<data name="ID0004" xml:space="preserve">
<value>The deserialized principal doesn't contain the mandatory 'oi_tkn_typ' claim.
When implementing custom token deserialization, a 'oi_tkn_typ' claim containing the type of the token being processed must be added to the security principal.</value>
</data>
<data name="ID0005" xml:space="preserve">
<value>The type of token associated with the deserialized principal ({0}) doesn't match one of the expected token types ({1}).</value>
</data>
<data name="ID0006" xml:space="preserve">
<value>A challenge response cannot be returned from this endpoint.</value>
</data>
<data name="ID0007" xml:space="preserve">
<value>The authentication context cannot be found.</value>
</data>
<data name="ID0008" xml:space="preserve">
<value>The device code identifier cannot be extracted from the principal.</value>
</data>
<data name="ID0009" xml:space="preserve">
<value>The token identifier cannot be extracted from the principal.</value>
</data>
<data name="ID0010" xml:space="preserve">
<value>A sign-in response cannot be returned from this endpoint.</value>
</data>
<data name="ID0011" xml:space="preserve">
<value>The specified principal is null or doesn't contain a claims-based identity.
Make sure that 'ClaimsPrincipal.Identity' is not null.</value>
</data>
<data name="ID0012" xml:space="preserve">
<value>The specified principal contains an authenticated identity, which is not valid when the sign-in operation is triggered from the device authorization or pushed authorization endpoints.
Make sure that 'ClaimsPrincipal.Identity.AuthenticationType' is null and that 'ClaimsPrincipal.Identity.IsAuthenticated' returns 'false'.</value>
</data>
<data name="ID0013" xml:space="preserve">
<value>The specified principal contains a subject claim, which is not valid when the sign-in operation is triggered from the device authorization or pushed authorization endpoints.</value>
</data>
<data name="ID0014" xml:space="preserve">
<value>The specified principal doesn't contain a valid/authenticated identity.
Make sure that 'ClaimsPrincipal.Identity.AuthenticationType' is not null and that 'ClaimsPrincipal.Identity.IsAuthenticated' returns 'true'.</value>
</data>
<data name="ID0015" xml:space="preserve">
<value>The specified principal was rejected because the mandatory subject claim was missing.</value>
</data>
<data name="ID0016" xml:space="preserve">
<value>The core services must be registered when enabling the OpenIddict server feature.
To register the OpenIddict core services, reference the 'OpenIddict.Core' package and call 'services.AddOpenIddict().AddCore()' from 'ConfigureServices'.
Alternatively, you can disable the built-in database-based server features by enabling the degraded mode with 'services.AddOpenIddict().AddServer().EnableDegradedMode()'.</value>
</data>
<data name="ID0017" xml:space="preserve">
<value>The application entry cannot be found in the database.</value>
</data>
<data name="ID0018" xml:space="preserve">
<value>An unknown error occurred while creating an authorization entry.</value>
</data>
<data name="ID0019" xml:space="preserve">
<value>An unknown error occurred while creating a token entry.</value>
</data>
<data name="ID0020" xml:space="preserve">
<value>A token entry cannot be created from a null principal or from a principal containing a null or invalid identity.</value>
</data>
<data name="ID0021" xml:space="preserve">
<value>The token entry cannot be found in the database.</value>
</data>
<data name="ID0022" xml:space="preserve">
<value>A token cannot be created from a null principal.</value>
</data>
<data name="ID0023" xml:space="preserve">
<value>The issuer must be a non-null, non-empty absolute URI.</value>
</data>
<data name="ID0024" xml:space="preserve">
<value>A sign-out response cannot be returned from this endpoint.</value>
</data>
<data name="ID0025" xml:space="preserve">
<value>The token type cannot be resolved.</value>
</data>
<data name="ID0026" xml:space="preserve">
<value>The payload associated with a reference token cannot be retrieved.
This may indicate that the token entry was corrupted.</value>
</data>
<data name="ID0027" xml:space="preserve">
<value>The authorization request was not correctly extracted.
To extract authorization requests, create a class implementing 'IOpenIddictServerHandler<ExtractAuthorizationRequestContext>' and register it using 'services.AddOpenIddict().AddServer().AddEventHandler()'.</value>
</data>
<data name="ID0028" xml:space="preserve">
<value>The request cannot be validated because no redirect_uri was specified.</value>
</data>
<data name="ID0029" xml:space="preserve">
<value>The authorization request was not handled.
To handle authorization requests in a controller, create a custom action with the same route as the authorization endpoint and enable the pass-through mode in the server ASP.NET Core or OWIN options using 'services.AddOpenIddict().AddServer().UseAspNetCore().EnableAuthorizationEndpointPassthrough()'.
Alternatively, create a class implementing 'IOpenIddictServerHandler<HandleAuthorizationRequestContext>' and register it using 'services.AddOpenIddict().AddServer().AddEventHandler()'.</value>
</data>
<data name="ID0030" xml:space="preserve">
<value>The authorization response was not correctly applied.
To apply authorization responses, create a class implementing 'IOpenIddictServerHandler<ApplyAuthorizationResponseContext>' and register it using 'services.AddOpenIddict().AddServer().AddEventHandler()'.</value>
</data>
<data name="ID0031" xml:space="preserve">
<value>The device authorization request was not correctly extracted.
To extract device authorization requests, create a class implementing 'IOpenIddictServerHandler<ExtractDeviceAuthorizationRequestContext>' and register it using 'services.AddOpenIddict().AddServer().AddEventHandler()'.</value>
</data>
<data name="ID0032" xml:space="preserve">
<value>The client application details cannot be found in the database.</value>
</data>
<data name="ID0033" xml:space="preserve">
<value>The device authorization response was not correctly applied.
To apply device authorization responses, create a class implementing 'IOpenIddictServerHandler<ApplyDeviceAuthorizationResponseContext>' and register it using 'services.AddOpenIddict().AddServer().AddEventHandler()'.</value>
</data>
<data name="ID0034" xml:space="preserve">
<value>The end-user verification request was not correctly extracted.
To extract end-user verification requests, create a class implementing 'IOpenIddictServerHandler<ExtractEndUserVerificationRequestContext>' and register it using 'services.AddOpenIddict().AddServer().AddEventHandler()'.</value>
</data>
<data name="ID0035" xml:space="preserve">
<value>The end-user verification request was not handled.
To handle end-user verification requests in a controller, create a custom action with the same route as the end-user verification endpoint and enable the pass-through mode in the server ASP.NET Core or OWIN options using 'services.AddOpenIddict().AddServer().UseAspNetCore().EnableVerificationEndpointPassthrough()'.
Alternatively, create a class implementing 'IOpenIddictServerHandler<HandleEndUserVerificationRequestContext>' and register it using 'services.AddOpenIddict().AddServer().AddEventHandler()'.</value>
</data>
<data name="ID0036" xml:space="preserve">
<value>The end-user verification response was not correctly applied.
To apply end-user verification responses, create a class implementing 'IOpenIddictServerHandler<ApplyEndUserVerificationResponseContext>' and register it using 'services.AddOpenIddict().AddServer().AddEventHandler()'.</value>
</data>
<data name="ID0037" xml:space="preserve">
<value>The configuration request was not correctly extracted.
To extract configuration requests, create a class implementing 'IOpenIddictServerHandler<ExtractConfigurationRequestContext>' and register it using 'services.AddOpenIddict().AddServer().AddEventHandler()'.</value>
</data>
<data name="ID0038" xml:space="preserve">
<value>The JSON Web Key Set request was not correctly extracted.
To extract configuration requests, create a class implementing 'IOpenIddictServerHandler<ExtractJsonWebKeySetRequestContext>' and register it using 'services.AddOpenIddict().AddServer().AddEventHandler()'.</value>
</data>
<data name="ID0039" xml:space="preserve">
<value>The JSON Web Key Set response was not correctly applied.
To apply JSON Web Key Set responses, create a class implementing 'IOpenIddictServerHandler<ApplyJsonWebKeySetResponseContext>' and register it using 'services.AddOpenIddict().AddServer().AddEventHandler()'.</value>
</data>
<data name="ID0040" xml:space="preserve">
<value>The token request was not correctly extracted.
To extract token requests, create a class implementing 'IOpenIddictServerHandler<ExtractTokenRequestContext>' and register it using 'services.AddOpenIddict().AddServer().AddEventHandler()'.</value>
</data>
<data name="ID0041" xml:space="preserve">
<value>The token request was not handled.
To handle token requests in a controller, create a custom action with the same route as the token endpoint and enable the pass-through mode in the server ASP.NET Core or OWIN options using 'services.AddOpenIddict().AddServer().UseAspNetCore().EnableTokenEndpointPassthrough()'.
Alternatively, create a class implementing 'IOpenIddictServerHandler<HandleTokenRequestContext>' and register it using 'services.AddOpenIddict().AddServer().AddEventHandler()'.</value>
</data>
<data name="ID0042" xml:space="preserve">
<value>The token response was not correctly applied.
To apply token responses, create a class implementing 'IOpenIddictServerHandler<ApplyTokenResponseContext>' and register it using 'services.AddOpenIddict().AddServer().AddEventHandler()'.</value>
</data>
<data name="ID0043" xml:space="preserve">
<value>The presenters list cannot be extracted from the authorization code.</value>
</data>
<data name="ID0044" xml:space="preserve">
<value>The presenters list cannot be extracted from the device code.</value>
</data>
<data name="ID0045" xml:space="preserve">
<value>The specified code challenge method is not supported.</value>
</data>
<data name="ID0046" xml:space="preserve">
<value>The introspection request was not correctly extracted.
To extract introspection requests, create a class implementing 'IOpenIddictServerHandler<ExtractIntrospectionRequestContext>' and register it using 'services.AddOpenIddict().AddServer().AddEventHandler()'.</value>
</data>
<data name="ID0047" xml:space="preserve">
<value>The introspection response was not correctly applied.
To apply introspection responses, create a class implementing 'IOpenIddictServerHandler<ApplyIntrospectionResponseContext>' and register it using 'services.AddOpenIddict().AddServer().AddEventHandler()'.</value>
</data>
<data name="ID0048" xml:space="preserve">
<value>The revocation request was not correctly extracted.
To extract revocation requests, create a class implementing 'IOpenIddictServerHandler<ExtractRevocationRequestContext>' and register it using 'services.AddOpenIddict().AddServer().AddEventHandler()'.</value>
</data>
<data name="ID0049" xml:space="preserve">
<value>The revocation response was not correctly applied.
To apply revocation responses, create a class implementing 'IOpenIddictServerHandler<ApplyRevocationResponseContext>' and register it using 'services.AddOpenIddict().AddServer().AddEventHandler()'.</value>
</data>
<data name="ID0050" xml:space="preserve">
<value>The end session request was not correctly extracted.
To extract end session requests, create a class implementing 'IOpenIddictServerHandler<ExtractEndSessionRequestContext>' and register it using 'services.AddOpenIddict().AddServer().AddEventHandler()'.</value>
</data>
<data name="ID0051" xml:space="preserve">
<value>The end session request was not handled.
To handle end session requests in a controller, create a custom controller action with the same route as the end session endpoint and enable the pass-through mode in the server ASP.NET Core or OWIN options using 'services.AddOpenIddict().AddServer().UseAspNetCore().EnableLogoutEndpointPassthrough()'.
Alternatively, create a class implementing 'IOpenIddictServerHandler<HandleEndSessionRequestContext>' and register it using 'services.AddOpenIddict().AddServer().AddEventHandler()'.</value>
</data>
<data name="ID0052" xml:space="preserve">
<value>The end session response was not correctly applied.
To apply end session responses, create a class implementing 'IOpenIddictServerHandler<ApplyEndSessionResponseContext>' and register it using 'services.AddOpenIddict().AddServer().AddEventHandler()'.</value>
</data>
<data name="ID0053" xml:space="preserve">
<value>The userinfo request was not correctly extracted.
To extract userinfo requests, create a class implementing 'IOpenIddictServerHandler<ExtractUserInfoRequestContext>' and register it using 'services.AddOpenIddict().AddServer().AddEventHandler()'.</value>
</data>
<data name="ID0054" xml:space="preserve">
<value>The userinfo response was not correctly applied.
To apply userinfo responses, create a class implementing 'IOpenIddictServerHandler<ApplyUserInfoResponseContext>' and register it using 'services.AddOpenIddict().AddServer().AddEventHandler()'.</value>
</data>
<data name="ID0055" xml:space="preserve">
<value>The asymmetric encryption key doesn't contain the required private key.</value>
</data>
<data name="ID0056" xml:space="preserve">
<value>An encryption algorithm cannot be automatically inferred from the encrypting key.
Consider using 'options.AddEncryptionCredentials(EncryptingCredentials)' instead.</value>
</data>
<data name="ID0057" xml:space="preserve">
<value>The algorithm cannot be null or empty.</value>
</data>
<data name="ID0058" xml:space="preserve">
<value>The specified algorithm is not supported.</value>
</data>
<data name="ID0059" xml:space="preserve">
<value>An unspecified error occurred while trying to change the key size of a System.Security.Cryptography.RSA instance of type '{0}'.</value>
</data>
<data name="ID0060" xml:space="preserve">
<value>The specified certificate is not a key encryption certificate.</value>
</data>
<data name="ID0061" xml:space="preserve">
<value>The specified certificate doesn't contain the required private key.</value>
</data>
<data name="ID0062" xml:space="preserve">
<value>The resource cannot be null or empty.</value>
</data>
<data name="ID0064" xml:space="preserve">
<value>The certificate was not found in the specified assembly.</value>
</data>
<data name="ID0065" xml:space="preserve">
<value>The thumbprint cannot be null or empty.</value>
</data>
<data name="ID0066" xml:space="preserve">
<value>The certificate corresponding to the specified thumbprint was not found.</value>
</data>
<data name="ID0067" xml:space="preserve">
<value>The asymmetric signing key doesn't contain the required private key.</value>
</data>
<data name="ID0068" xml:space="preserve">
<value>A signature algorithm cannot be automatically inferred from the signing key.
Consider using 'options.AddSigningCredentials(SigningCredentials)' instead.</value>
</data>
<data name="ID0069" xml:space="preserve">
<value>ECDSA signing keys are not supported on this platform.</value>
</data>
<data name="ID0070" xml:space="preserve">
<value>The specified certificate is not a signing certificate.</value>
</data>
<data name="ID0071" xml:space="preserve">
<value>The grant type cannot be null or empty.</value>
</data>
<data name="ID0072" xml:space="preserve">
<value>Endpoint URIs must be valid URIs.</value>
</data>
<data name="ID0075" xml:space="preserve">
<value>The security token handler cannot be null.</value>
</data>
<data name="ID0076" xml:space="preserve">
<value>At least one OAuth 2.0/OpenID Connect flow must be enabled.</value>
</data>
<data name="ID0077" xml:space="preserve">
<value>The authorization endpoint must be enabled to use the authorization code and implicit flows.</value>
</data>
<data name="ID0078" xml:space="preserve">
<value>The device authorization endpoint must be enabled to use the device authorization flow.</value>
</data>
<data name="ID0079" xml:space="preserve">
<value>The token endpoint must be enabled to use the authorization code, client credentials, device, password and refresh token flows.</value>
</data>
<data name="ID0080" xml:space="preserve">
<value>The end-user verification endpoint must be enabled to use the device authorization flow.</value>
</data>
<data name="ID0081" xml:space="preserve">
<value>Endpoint URIs cannot start with '{0}'.</value>
</data>
<data name="ID0082" xml:space="preserve">
<value>Dependency injection support must be enabled in Quartz.NET when using the OpenIddict integration.
To enable DI support, call 'services.AddQuartz(options => options.UseMicrosoftDependencyInjectionJobFactory())' or 'services.AddQuartz(options => options.UseMicrosoftDependencyInjectionScopedJobFactory())'.</value>
</data>
<data name="ID0083" xml:space="preserve">
<value>Reference tokens cannot be used when disabling token storage.</value>
</data>
<data name="ID0084" xml:space="preserve">
<value>The device grant must be allowed when enabling the device authorization endpoint.</value>
</data>
<data name="ID0085" xml:space="preserve">
<value>At least one encryption key must be registered in the OpenIddict server options.
Consider registering a certificate using 'services.AddOpenIddict().AddServer().AddEncryptionCertificate()' or 'services.AddOpenIddict().AddServer().AddDevelopmentEncryptionCertificate()' or call 'services.AddOpenIddict().AddServer().AddEphemeralEncryptionKey()' to use an ephemeral key.</value>
</data>
<data name="ID0086" xml:space="preserve">
<value>At least one asymmetric signing key must be registered in the OpenIddict server options.
Consider registering a certificate using 'services.AddOpenIddict().AddServer().AddSigningCertificate()' or 'services.AddOpenIddict().AddServer().AddDevelopmentSigningCertificate()' or call 'services.AddOpenIddict().AddServer().AddEphemeralSigningKey()' to use an ephemeral key.</value>
</data>
<data name="ID0087" xml:space="preserve">
<value>When using X.509 encryption credentials, at least one of the registered certificates must be valid.
To use key rollover, register both the new certificate and the old one in the credentials collection.</value>
</data>
<data name="ID0088" xml:space="preserve">
<value>When using X.509 signing credentials, at least one of the registered certificates must be valid.
To use key rollover, register both the new certificate and the old one in the credentials collection.</value>
</data>
<data name="ID0089" xml:space="preserve">
<value>No custom authorization request validation handler was found. When enabling the degraded mode, a custom 'IOpenIddictServerHandler<ValidateAuthorizationRequestContext>' must be implemented to validate authorization requests (e.g to ensure the client_id and redirect_uri are valid).</value>
</data>
<data name="ID0090" xml:space="preserve">
<value>No custom device authorization request validation handler was found. When enabling the degraded mode, a custom 'IOpenIddictServerHandler<ValidateDeviceAuthorizationRequestContext>' (or 'IOpenIddictServerHandler<ProcessAuthenticationContext>') must be implemented to validate device authorization requests (e.g to ensure the client_id and client_secret are valid).</value>
</data>
<data name="ID0091" xml:space="preserve">
<value>No custom introspection request validation handler was found. When enabling the degraded mode, a custom 'IOpenIddictServerHandler<ValidateIntrospectionRequestContext>' (or 'IOpenIddictServerHandler<ProcessAuthenticationContext>') must be implemented to validate introspection requests (e.g to ensure the client_id and client_secret are valid).</value>
</data>
<data name="ID0092" xml:space="preserve">
<value>No custom end session request validation handler was found. When enabling the degraded mode, a custom 'IOpenIddictServerHandler<ValidateEndSessionRequestContext>' must be implemented to validate end session requests (e.g to ensure the post_logout_redirect_uri is valid).</value>
</data>
<data name="ID0093" xml:space="preserve">
<value>No custom revocation request validation handler was found. When enabling the degraded mode, a custom 'IOpenIddictServerHandler<ValidateRevocationRequestContext>' (or 'IOpenIddictServerHandler<ProcessAuthenticationContext>') must be implemented to validate revocation requests (e.g to ensure the client_id and client_secret are valid).</value>
</data>
<data name="ID0094" xml:space="preserve">
<value>No custom token request validation handler was found. When enabling the degraded mode, a custom 'IOpenIddictServerHandler<ValidateTokenRequestContext>' (or 'IOpenIddictServerHandler<ProcessAuthenticationContext>') must be implemented to validate token requests (e.g to ensure the client_id and client_secret are valid).</value>
</data>
<data name="ID0095" xml:space="preserve">
<value>No custom end-user verification request validation handler was found. When enabling the degraded mode, a custom 'IOpenIddictServerHandler<ValidateEndUserVerificationRequestContext>' must be implemented to validate verification requests (e.g to ensure the user_code is valid).</value>
</data>
<data name="ID0096" xml:space="preserve">
<value>No custom token validation handler was found. When enabling the degraded mode, a custom 'IOpenIddictServerHandler<ValidateTokenContext>' must be implemented to handle device and user codes (e.g by retrieving them from a database).</value>
</data>
<data name="ID0097" xml:space="preserve">
<value>No custom token generation handler was found. When enabling the degraded mode, a custom 'IOpenIddictServerHandler<GenerateTokenContext>' must be implemented to handle device and user codes (e.g by storing them in a database).</value>
</data>
<data name="ID0098" xml:space="preserve">
<value>The event handler of type '{0}' couldn't be resolved.
This may indicate that it was not properly registered in the dependency injection container. To register an event handler, use 'services.AddOpenIddict().AddServer().AddEventHandler()'.</value>
</data>
<data name="ID0099" xml:space="preserve">
<value>The event handler filter of type '{0}' couldn't be resolved.
This may indicate that it was not properly registered in the dependency injection container.</value>
</data>
<data name="ID0100" xml:space="preserve">
<value>The redirect_uri cannot be null or empty.</value>
</data>
<data name="ID0101" xml:space="preserve">
<value>The authorization request cannot be validated because a different redirect_uri was specified by the client application.</value>
</data>
<data name="ID0102" xml:space="preserve">
<value>The post_logout_redirect_uri cannot be null or empty.</value>
</data>
<data name="ID0103" xml:space="preserve">
<value>The end session request cannot be validated because a different post_logout_redirect_uri was specified by the client application.</value>
</data>
<data name="ID0104" xml:space="preserve">
<value>The specified service type is not valid.</value>
</data>
<data name="ID0105" xml:space="preserve">
<value>No service descriptor was set.</value>
</data>
<data name="ID0106" xml:space="preserve">
<value>The property name cannot be null or empty.</value>
</data>
<data name="ID0107" xml:space="preserve">
<value>The realm cannot be null or empty.</value>
</data>
<data name="ID0108" xml:space="preserve">
<value>The OpenIddict ASP.NET Core server handler cannot be registered as an authentication scheme.
This may indicate that an instance of another handler was registered with the same scheme.</value>
</data>
<data name="ID0109" xml:space="preserve">
<value>The OpenIddict ASP.NET Core server handler cannot be used as the default scheme handler.
Make sure that neither DefaultAuthenticateScheme, DefaultChallengeScheme, DefaultForbidScheme, DefaultSignInScheme, DefaultSignOutScheme nor DefaultScheme point to an instance of the OpenIddict ASP.NET Core server handler.</value>
</data>
<data name="ID0110" xml:space="preserve">
<value>The error pass-through mode cannot be used when the status code pages integration is enabled.</value>
</data>
<data name="ID0111" xml:space="preserve">
<value>The OpenID Connect response was not correctly processed.
This may indicate that the event handler responsible for processing OpenID Connect responses was not registered or was explicitly removed from the handlers list.</value>
</data>
<data name="ID0112" xml:space="preserve">
<value>An error occurred while retrieving the OpenIddict server context. On ASP.NET Core, this may indicate that the authentication middleware was not registered early enough in the request pipeline. Make sure that 'app.UseAuthentication()' is registered before 'app.UseAuthorization()' and 'app.UseEndpoints()' (or 'app.UseMvc()') and try again.</value>
</data>
<data name="ID0113" xml:space="preserve">
<value>An error occurred while authenticating the current request.</value>
</data>
<data name="ID0114" xml:space="preserve">
<value>The ASP.NET Core HTTP request cannot be resolved.</value>
</data>
<data name="ID0115" xml:space="preserve">
<value>Only strings, booleans, integers, arrays of strings and instances of type 'OpenIddictParameter', 'JsonElement' or derived from 'JsonNode' can be returned as custom parameters.</value>
</data>
<data name="ID0119" xml:space="preserve">
<value>The OpenIddict OWIN server handler cannot be used as an active authentication handler.
Make sure that 'OpenIddictServerOwinOptions.AuthenticationMode' is not set to 'Active'.</value>
</data>
<data name="ID0120" xml:space="preserve">
<value>The OWIN request cannot be resolved.</value>
</data>
<data name="ID0121" xml:space="preserve">
<value>No service provider was found in the OWIN context.
For the OpenIddict server services to work correctly, a per-request 'IServiceProvider' must be attached to the OWIN environment with the dictionary key 'System.IServiceProvider'.
Note: when using a dependency injection container supporting middleware resolution (like Autofac), the 'app.UseOpenIddictServer()' extension MUST NOT be called.</value>
</data>
<data name="ID0122" xml:space="preserve">
<value>The OpenIddict server services cannot be resolved from the DI container.
To register the server services, use 'services.AddOpenIddict().AddServer()'.</value>
</data>
<data name="ID0123" xml:space="preserve">
<value>Audiences cannot be null or empty.</value>
</data>
<data name="ID0124" xml:space="preserve">
<value>The client identifier cannot be null or empty.</value>
</data>
<data name="ID0125" xml:space="preserve">
<value>The client secret cannot be null or empty.</value>
</data>
<data name="ID0126" xml:space="preserve">
<value>The issuer cannot be null or empty.</value>
</data>
<data name="ID0127" xml:space="preserve">
<value>The base URI or request URI cannot be retrieved from the request context or are not valid absolute URIs.</value>
</data>
<data name="ID0128" xml:space="preserve">
<value>An OAuth 2.0/OpenID Connect server configuration or an issuer URI must be registered.
To use a local OpenIddict server, reference the 'OpenIddict.Validation.ServerIntegration' package and call 'services.AddOpenIddict().AddValidation().UseLocalServer()' to import the server settings.
To use a remote server, reference the 'OpenIddict.Validation.SystemNetHttp' package and call 'services.AddOpenIddict().AddValidation().UseSystemNetHttp()' and 'services.AddOpenIddict().AddValidation().SetIssuer()' to use server discovery.
Alternatively, you can register a static server configuration by calling 'services.AddOpenIddict().AddValidation().SetConfiguration()'.</value>
</data>
<data name="ID0129" xml:space="preserve">
<value>An introspection client must be registered when using introspection.
Reference the 'OpenIddict.Validation.SystemNetHttp' package and call 'services.AddOpenIddict().AddValidation().UseSystemNetHttp()' to register the default System.Net.Http-based integration.</value>
</data>
<data name="ID0130" xml:space="preserve">
<value>The issuer or the configuration endpoint URI must be set when using introspection.</value>
</data>
<data name="ID0131" xml:space="preserve">
<value>The client identifier cannot be null or empty when using introspection.</value>
</data>
<data name="ID0132" xml:space="preserve">
<value>The client secret cannot be null or empty when using introspection. Alternatively, one or multiple signing credentials can be registered and used to produce client assertions if the authorization server supports this client authentication method.</value>
</data>
<data name="ID0133" xml:space="preserve">
<value>Authorization entry validation cannot be enabled when using introspection.</value>
</data>
<data name="ID0134" xml:space="preserve">
<value>Token entry validation cannot be enabled when using introspection.</value>
</data>
<data name="ID0135" xml:space="preserve">
<value>A discovery client must be registered when using server discovery.
Reference the 'OpenIddict.Validation.SystemNetHttp' package and call 'services.AddOpenIddict().AddValidation().UseSystemNetHttp()' to register the default System.Net.Http-based integration.</value>
</data>
<data name="ID0136" xml:space="preserve">
<value>The issuer must be a valid absolute URI.</value>
</data>
<data name="ID0137" xml:space="preserve">
<value>The issuer cannot contain a fragment or a query string.</value>
</data>
<data name="ID0138" xml:space="preserve">
<value>The event handler of type '{0}' couldn't be resolved.
This may indicate that it was not properly registered in the dependency injection container. To register an event handler, use 'services.AddOpenIddict().AddValidation().AddEventHandler()'.</value>
</data>
<data name="ID0139" xml:space="preserve">
<value>The core services must be registered when enabling token entry validation.
To register the OpenIddict core services, reference the 'OpenIddict.Core' package and call 'services.AddOpenIddict().AddCore()' from 'ConfigureServices'.</value>
</data>
<data name="ID0140" xml:space="preserve">
<value>An unknown error occurred while retrieving the server configuration.</value>
</data>
<data name="ID0141" xml:space="preserve">
<value>An unknown error occurred while introspecting the access token.</value>
</data>
<data name="ID0142" xml:space="preserve">
<value>The core services must be registered when enabling authorization entry validation.
To register the OpenIddict core services, reference the 'OpenIddict.Core' package and call 'services.AddOpenIddict().AddCore()' from 'ConfigureServices'.</value>
</data>
<data name="ID0143" xml:space="preserve">
<value>The URI cannot be null or empty.</value>
</data>
<data name="ID0144" xml:space="preserve">
<value>The URI must be a valid absolute URI.</value>
</data>
<data name="ID0145" xml:space="preserve">
<value>The server configuration couldn't be retrieved.</value>
</data>
<data name="ID0146" xml:space="preserve">
<value>The JSON Web Key Set URI couldn't be resolved from the provider metadata.</value>
</data>
<data name="ID0147" xml:space="preserve">
<value>The server JSON Web Key set couldn't be retrieved.</value>
</data>
<data name="ID0148" xml:space="preserve">
<value>An error occurred while preparing the configuration request.
Error: {0}
Error description: {1}
Error URI: {2}</value>
</data>
<data name="ID0149" xml:space="preserve">
<value>An error occurred while sending the configuration request.
Error: {0}
Error description: {1}
Error URI: {2}</value>
</data>
<data name="ID0150" xml:space="preserve">
<value>An error occurred while extracting the configuration response.
Error: {0}
Error description: {1}
Error URI: {2}</value>
</data>
<data name="ID0151" xml:space="preserve">
<value>An error occurred while handling the configuration response.
Error: {0}
Error description: {1}
Error URI: {2}</value>
</data>
<data name="ID0152" xml:space="preserve">
<value>An error occurred while preparing the JSON Web Key Set request.
Error: {0}
Error description: {1}
Error URI: {2}</value>
</data>
<data name="ID0153" xml:space="preserve">
<value>An error occurred while sending the JSON Web Key Set request.
Error: {0}
Error description: {1}
Error URI: {2}</value>
</data>
<data name="ID0154" xml:space="preserve">
<value>An error occurred while extracting the JSON Web Key Set response.
Error: {0}
Error description: {1}
Error URI: {2}</value>
</data>
<data name="ID0155" xml:space="preserve">
<value>An error occurred while handling the JSON Web Key Set response.
Error: {0}
Error description: {1}
Error URI: {2}</value>
</data>
<data name="ID0156" xml:space="preserve">
<value>The token cannot be null or empty.</value>
</data>
<data name="ID0157" xml:space="preserve">
<value>An unknown error occurred while introspecting the token.</value>
</data>
<data name="ID0158" xml:space="preserve">
<value>An error occurred while preparing the introspection request.
Error: {0}
Error description: {1}
Error URI: {2}</value>
</data>
<data name="ID0159" xml:space="preserve">
<value>An error occurred while sending the introspection request.
Error: {0}
Error description: {1}
Error URI: {2}</value>
</data>
<data name="ID0160" xml:space="preserve">
<value>An error occurred while extracting the introspection response.
Error: {0}
Error description: {1}
Error URI: {2}</value>
</data>
<data name="ID0161" xml:space="preserve">
<value>An error occurred while handling the introspection response.
Error: {0}
Error description: {1}
Error URI: {2}</value>
</data>
<data name="ID0162" xml:space="preserve">
<value>The access token cannot be null or empty.</value>
</data>
<data name="ID0163" xml:space="preserve">
<value>An error occurred while validating the access token.
Error: {0}
Error description: {1}
Error URI: {2}</value>
</data>
<data name="ID0164" xml:space="preserve">
<value>The OpenIddict ASP.NET Core validation handler cannot be registered as an authentication scheme.
This may indicate that an instance of another handler was registered with the same scheme.</value>
</data>
<data name="ID0165" xml:space="preserve">
<value>The OpenIddict ASP.NET Core validation handler cannot be used as the default sign-in/sign-out handler.
Make sure that neither DefaultSignInScheme nor DefaultSignOutScheme point to an instance of the OpenIddict ASP.NET Core validation handler.</value>
</data>
<data name="ID0166" xml:space="preserve">
<value>An error occurred while retrieving the OpenIddict validation context. On ASP.NET Core, this may indicate that the authentication middleware was not registered early enough in the request pipeline. Make sure that 'app.UseAuthentication()' is registered before 'app.UseAuthorization()' and 'app.UseEndpoints()' (or 'app.UseMvc()') and try again.</value>
</data>
<data name="ID0167" xml:space="preserve">
<value>Generic token validation is not supported by the validation handler.</value>
</data>
<data name="ID0168" xml:space="preserve">
<value>No service provider was found in the OWIN context.
For the OpenIddict validation services to work correctly, a per-request 'IServiceProvider' must be attached to the OWIN environment with the dictionary key 'System.IServiceProvider'.
Note: when using a dependency injection container supporting middleware resolution (like Autofac), the 'app.UseOpenIddictValidation()' extension MUST NOT be called.</value>
</data>
<data name="ID0169" xml:space="preserve">
<value>The OpenIddict validation services cannot be resolved from the DI container.
To register the validation services, use 'services.AddOpenIddict().AddValidation()'.</value>
</data>
<data name="ID0170" xml:space="preserve">
<value>The local server integration can only be used with direct validation.</value>
</data>
<data name="ID0171" xml:space="preserve">
<value>Authorization entry validation cannot be enabled when authorization storage is disabled in the OpenIddict server options.</value>
</data>
<data name="ID0172" xml:space="preserve">
<value>Token entry validation cannot be enabled when token storage is disabled in the OpenIddict server options.</value>
</data>
<data name="ID0173" xml:space="preserve">
<value>The System.Net.Http request cannot be resolved.</value>
</data>
<data name="ID0174" xml:space="preserve">
<value>An unknown error occurred while creating a System.Net.Http client.</value>
</data>
<data name="ID0175" xml:space="preserve">
<value>An unknown error occurred while sending a System.Net.Http request.</value>
</data>
<data name="ID0176" xml:space="preserve">
<value>The specified type is not supported.</value>
</data>
<data name="ID0177" xml:space="preserve">
<value>The value cannot be null or empty.</value>
</data>
<data name="ID0178" xml:space="preserve">
<value>The prompt cannot be null or empty.</value>
</data>
<data name="ID0179" xml:space="preserve">
<value>The response type cannot be null or empty.</value>
</data>
<data name="ID0180" xml:space="preserve">
<value>The scope cannot be null or empty.</value>
</data>
<data name="ID0181" xml:space="preserve">
<value>The destination cannot be null or empty.</value>
</data>
<data name="ID0182" xml:space="preserve">
<value>Destinations cannot be null or empty.</value>
</data>
<data name="ID0183" xml:space="preserve">
<value>Conflicting destinations for the claim '{0}' were specified.</value>
</data>
<data name="ID0184" xml:space="preserve">
<value>The claim type cannot be null or empty.</value>
</data>
<data name="ID0185" xml:space="preserve">
<value>The claim value is not a supported JSON node.</value>
</data>
<data name="ID0186" xml:space="preserve">
<value>The audience cannot be null or empty.</value>
</data>
<data name="ID0187" xml:space="preserve">
<value>The presenter cannot be null or empty.</value>
</data>
<data name="ID0188" xml:space="preserve">
<value>The token type cannot be null or empty.</value>
</data>
<data name="ID0189" xml:space="preserve">
<value>The specified JSON element is not an object.</value>
</data>
<data name="ID0190" xml:space="preserve">
<value>The parameter name cannot be null or empty.</value>
</data>
<data name="ID0191" xml:space="preserve">
<value>A parameter with the same name already exists.</value>
</data>
<data name="ID0192" xml:space="preserve">
<value>The item name cannot be null or empty.</value>
</data>
<data name="ID0193" xml:space="preserve">
<value>The item index cannot be negative.</value>
</data>
<data name="ID0194" xml:space="preserve">
<value>The specified '{0}' setting is not valid.</value>
</data>
<data name="ID0195" xml:space="preserve">
<value>The identifier cannot be null or empty.</value>
</data>
<data name="ID0196" xml:space="preserve">
<value>The application identifier cannot be extracted.</value>
</data>
<data name="ID0197" xml:space="preserve">
<value>An error occurred while creating an expiration signal.</value>
</data>
<data name="ID0198" xml:space="preserve">
<value>The subject cannot be null or empty.</value>
</data>
<data name="ID0199" xml:space="preserve">
<value>The status cannot be null or empty.</value>
</data>
<data name="ID0200" xml:space="preserve">
<value>The type cannot be null or empty.</value>
</data>
<data name="ID0201" xml:space="preserve">
<value>The authorization identifier cannot be extracted.</value>
</data>
<data name="ID0202" xml:space="preserve">
<value>The scope name cannot be null or empty.</value>
</data>
<data name="ID0203" xml:space="preserve">
<value>Scope names cannot be null or empty.</value>
</data>
<data name="ID0204" xml:space="preserve">
<value>The scope identifier cannot be extracted.</value>
</data>
<data name="ID0205" xml:space="preserve">
<value>The token identifier cannot be extracted.</value>
</data>
<data name="ID0206" xml:space="preserve">
<value>The client secret hash cannot be set on the application entity.</value>
</data>
<data name="ID0207" xml:space="preserve">
<value>One or more validation error(s) occurred while trying to create a new application:</value>
</data>
<data name="ID0208" xml:space="preserve">
<value>An error occurred while trying to create a new application.</value>
</data>
<data name="ID0209" xml:space="preserve">
<value>The client type cannot be null or empty.</value>
</data>
<data name="ID0210" xml:space="preserve">
<value>The consent type cannot be null or empty.</value>
</data>
<data name="ID0211" xml:space="preserve">
<value>The permission name cannot be null or empty.</value>
</data>
<data name="ID0212" xml:space="preserve">
<value>The requirement name cannot be null or empty.</value>
</data>
<data name="ID0213" xml:space="preserve">
<value>Callback URIs cannot be null or empty.</value>
</data>
<data name="ID0214" xml:space="preserve">
<value>Callback URIs must be valid absolute URIs.</value>
</data>
<data name="ID0215" xml:space="preserve">
<value>One or more validation error(s) occurred while trying to update an existing application:</value>
</data>
<data name="ID0216" xml:space="preserve">
<value>The secret cannot be null or empty.</value>
</data>
<data name="ID0217" xml:space="preserve">
<value>The specified hash algorithm is not valid.</value>
</data>
<data name="ID0218" xml:space="preserve">
<value>The comparand cannot be null or empty.</value>
</data>
<data name="ID0219" xml:space="preserve">
<value>One or more validation error(s) occurred while trying to create a new authorization:</value>
</data>
<data name="ID0220" xml:space="preserve">
<value>An error occurred while trying to create a new authorization.</value>
</data>
<data name="ID0221" xml:space="preserve">
<value>One or more validation error(s) occurred while trying to update an existing authorization:</value>
</data>
<data name="ID0222" xml:space="preserve">
<value>One or more validation error(s) occurred while trying to create a new scope:</value>
</data>
<data name="ID0223" xml:space="preserve">
<value>An error occurred while trying to create a new scope.</value>
</data>
<data name="ID0224" xml:space="preserve">
<value>One or more validation error(s) occurred while trying to update an existing scope:</value>
</data>
<data name="ID0225" xml:space="preserve">
<value>One or more validation error(s) occurred while trying to create a new token:</value>
</data>
<data name="ID0226" xml:space="preserve">
<value>An error occurred while trying to create a new token.</value>
</data>
<data name="ID0227" xml:space="preserve">
<value>One or more validation error(s) occurred while trying to update an existing token:</value>
</data>
<data name="ID0228" xml:space="preserve">
<value>No application store has been registered in the dependency injection container.
To register the Entity Framework Core stores, reference the 'OpenIddict.EntityFrameworkCore' package and call 'services.AddOpenIddict().AddCore().UseEntityFrameworkCore()'.
To register a custom store, create an implementation of 'IOpenIddictApplicationStore' and use 'services.AddOpenIddict().AddCore().AddApplicationStore()' to add it to the DI container.</value>
</data>
<data name="ID0229" xml:space="preserve">
<value>No authorization store has been registered in the dependency injection container.
To register the Entity Framework Core stores, reference the 'OpenIddict.EntityFrameworkCore' package and call 'services.AddOpenIddict().AddCore().UseEntityFrameworkCore()'.
To register a custom store, create an implementation of 'IOpenIddictAuthorizationStore' and use 'services.AddOpenIddict().AddCore().AddAuthorizationStore()' to add it to the DI container.</value>
</data>
<data name="ID0230" xml:space="preserve">
<value>No scope store has been registered in the dependency injection container.
To register the Entity Framework Core stores, reference the 'OpenIddict.EntityFrameworkCore' package and call 'services.AddOpenIddict().AddCore().UseEntityFrameworkCore()'.
To register a custom store, create an implementation of 'IOpenIddictScopeStore' and use 'services.AddOpenIddict().AddCore().AddScopeStore()' to add it to the DI container.</value>
</data>
<data name="ID0231" xml:space="preserve">
<value>No token store has been registered in the dependency injection container.
To register the Entity Framework Core stores, reference the 'OpenIddict.EntityFrameworkCore' package and call 'services.AddOpenIddict().AddCore().UseEntityFrameworkCore()'.
To register a custom store, create an implementation of 'IOpenIddictTokenStore' and use 'services.AddOpenIddict().AddCore().AddTokenStore()' to add it to the DI container.</value>
</data>
<data name="ID0232" xml:space="preserve">
<value>The specified type is invalid.</value>
</data>
<data name="ID0233" xml:space="preserve">
<value>The cache size cannot be less than 10.</value>
</data>
<data name="ID0234" xml:space="preserve">
<value>The specified application type is not compatible with the Entity Framework 6.x stores.
When enabling the Entity Framework 6.x stores, make sure you use the built-in 'OpenIddictEntityFrameworkApplication' entity or a custom entity that inherits from the generic 'OpenIddictEntityFrameworkApplication' entity.</value>
</data>
<data name="ID0235" xml:space="preserve">
<value>No Entity Framework 6.x context was specified in the OpenIddict options.
To configure the OpenIddict Entity Framework 6.x stores to use a specific 'DbContext', use 'options.UseEntityFramework().UseDbContext<TContext>()'.</value>
</data>
<data name="ID0236" xml:space="preserve">
<value>The specified authorization type is not compatible with the Entity Framework 6.x stores.
When enabling the Entity Framework 6.x stores, make sure you use the built-in 'OpenIddictEntityFrameworkAuthorization' entity or a custom entity that inherits from the generic 'OpenIddictEntityFrameworkAuthorization' entity.</value>
</data>
<data name="ID0237" xml:space="preserve">
<value>The specified scope type is not compatible with the Entity Framework 6.x stores.
When enabling the Entity Framework 6.x stores, make sure you use the built-in 'OpenIddictEntityFrameworkScope' entity or a custom entity that inherits from the generic 'OpenIddictEntityFrameworkScope' entity.</value>
</data>
<data name="ID0238" xml:space="preserve">
<value>The specified token type is not compatible with the Entity Framework 6.x stores.
When enabling the Entity Framework 6.x stores, make sure you use the built-in 'OpenIddictEntityFrameworkToken' entity or a custom entity that inherits from the generic 'OpenIddictEntityFrameworkToken' entity.</value>
</data>
<data name="ID0239" xml:space="preserve">
<value>The application was concurrently updated and cannot be persisted in its current state.
Reload the application from the database and retry the operation.</value>
</data>
<data name="ID0240" xml:space="preserve">
<value>An error occurred while trying to create a new application instance.
Make sure that the application entity is not abstract and has a public parameterless constructor or create a custom application store that overrides 'InstantiateAsync()' to use a custom factory.</value>
</data>
<data name="ID0241" xml:space="preserve">
<value>The authorization was concurrently updated and cannot be persisted in its current state.
Reload the authorization from the database and retry the operation.</value>
</data>
<data name="ID0242" xml:space="preserve">
<value>An error occurred while trying to create a new authorization instance.
Make sure that the authorization entity is not abstract and has a public parameterless constructor or create a custom authorization store that overrides 'InstantiateAsync()' to use a custom factory.</value>
</data>
<data name="ID0243" xml:space="preserve">
<value>An error occurred while pruning authorizations.</value>
</data>
<data name="ID0244" xml:space="preserve">
<value>The application associated with the authorization cannot be found.</value>
</data>
<data name="ID0245" xml:space="preserve">
<value>The scope was concurrently updated and cannot be persisted in its current state.
Reload the scope from the database and retry the operation.</value>
</data>
<data name="ID0246" xml:space="preserve">
<value>An error occurred while trying to create a new scope instance.
Make sure that the scope entity is not abstract and has a public parameterless constructor or create a custom scope store that overrides 'InstantiateAsync()' to use a custom factory.</value>
</data>
<data name="ID0247" xml:space="preserve">
<value>The token was concurrently updated and cannot be persisted in its current state.
Reload the token from the database and retry the operation.</value>
</data>
<data name="ID0248" xml:space="preserve">
<value>An error occurred while trying to create a new token instance.
Make sure that the token entity is not abstract and has a public parameterless constructor or create a custom token store that overrides 'InstantiateAsync()' to use a custom factory.</value>
</data>
<data name="ID0249" xml:space="preserve">
<value>An error occurred while pruning tokens.</value>
</data>
<data name="ID0250" xml:space="preserve">
<value>The application associated with the token cannot be found.</value>
</data>
<data name="ID0251" xml:space="preserve">
<value>The authorization associated with the token cannot be found.</value>
</data>
<data name="ID0252" xml:space="preserve">
<value>The specified application type is not compatible with the Entity Framework Core stores.
When enabling the Entity Framework Core stores, make sure you use the built-in 'OpenIddictEntityFrameworkCoreApplication' entity or a custom entity that inherits from the generic 'OpenIddictEntityFrameworkCoreApplication' entity.</value>
</data>
<data name="ID0253" xml:space="preserve">
<value>No Entity Framework Core context was specified in the OpenIddict options.
To configure the OpenIddict Entity Framework Core stores to use a specific 'DbContext', use 'options.UseEntityFrameworkCore().UseDbContext<TContext>()'.</value>
</data>
<data name="ID0254" xml:space="preserve">
<value>The specified authorization type is not compatible with the Entity Framework Core stores.
When enabling the Entity Framework Core stores, make sure you use the built-in 'OpenIddictEntityFrameworkCoreAuthorization' entity or a custom entity that inherits from the generic 'OpenIddictEntityFrameworkCoreAuthorization' entity.</value>
</data>
<data name="ID0255" xml:space="preserve">
<value>The specified scope type is not compatible with the Entity Framework Core stores.
When enabling the Entity Framework Core stores, make sure you use the built-in 'OpenIddictEntityFrameworkCoreScope' entity or a custom entity that inherits from the generic 'OpenIddictEntityFrameworkCoreScope' entity.</value>
</data>
<data name="ID0256" xml:space="preserve">
<value>The specified token type is not compatible with the Entity Framework Core stores.
When enabling the Entity Framework Core stores, make sure you use the built-in 'OpenIddictEntityFrameworkCoreToken' entity or a custom entity that inherits from the generic 'OpenIddictEntityFrameworkCoreToken' entity.</value>
</data>
<data name="ID0257" xml:space="preserve">
<value>The specified application type is not compatible with the MongoDB stores.
When enabling the MongoDB stores, make sure you use the built-in 'OpenIddictMongoDbApplication' entity or a custom entity that inherits from the 'OpenIddictMongoDbApplication' entity.</value>
</data>