Why am I getting a NoClassDefFoundError FATAL EXCEPTION in my AAA application?
After declaring a dependency on a AAA library and compiling an application, it is possible that the application will crash after issuing an error. e.g., you may see a stacktrace similar to this one:
What are the best strategies/restrictions with regards to removing/deleting users from the addressbook?
The administrator with the user management authorization can delete a user while the user is not logged in. A user can not delete himself.
The SmartSDK custom authentication mechanism requires the logged in user to be registered in the address book. There are two strategies to eliminate or reduce the user information in the address book.
(a) delete the user from the address book AFTER the user logs out
(b) register the user with a temporary user information
(a) Delete the user from the address book AFTER the user logs out
Can a Custom Authentication application allow a username to have blank spaces?
No. The current SmartSDK specification does not allow blank spaces in the USER_ID parameter for the REQ_LOGIN intent. The USER_ID can be up to 32 bytes and cannot include blank spaces, colon and double quotation mark (“) characters.
How do I correctly set the display name on the top left of the home screen?
If your application is a custom authentication application, using the RES_EXTERNAL_AUTH you have the ability to return values for the following: userid, user name and display name. You’ll want to use the “user name” key to display the value that you intended too on the top left of the home screen. Keep in mind the “display name” is the key to specify the name in the machine addressbook UI.
How to get current user name/useID who is logged in on the MFP device?
Using the SDKService
AndroidManifest.xml
<receiver android:name=".Application"
android:permission="jp.co.ricoh.isdk.sdkservice.common.SdkService.APP_EVENT_PERMISSION">
<intent-filter>
<action android:name="jp.co.ricoh.isdk.sdkservice.auth.GET_AUTH_STATE"/>
</intent-filter>
</receiver>
Application*.java
When Custom Auth is ON print job is rejected with the message Access Restricted in the Printer Job History. Why?
There are two reasons why this would occur:
1. Put off the authentication for Printer function
Printer Authentication ON/OFF setting SP5-420-041 OFF(1)/ON(0) Default ON(0)
The user authentication for printer job is disable by setting this SP set to "OFF" (1). This setting has an effectiveness for all print job including standard print app and/or media print app. Because the login request is not issued for any print job.
What are the SP mode settings for Custom Authentication (InternalLoginModule)?
The SP Modes for InternalLoginModule are as follows:
InternalLoginModule please change:
* SP 5-401-230 from 0 to 1
* SP 5-401-103 from 0 to 3
Always be sure to restart the device the device following any changes in SP mode.
What are the CAP field length size specifications?
CAP Specs:
Login User Name Up to 128 characters
—
Name Up to 20 characters
—
Key Display Name Up to 16 characters
—
Domain Name Up to 255 bytes
—
Login Password Up to 128 characters
—
Email Address Up to 128 characters
—
Fax Destination Up to 128 characters
—
FYI -
One constrain is an issue with older Window's active directory server and the other is the actual CAP field length specs.