Hello Kondal, when you imported the Pega Robotic Automation Package and the Automation Package Management, do you know if the robotics and robotics SSO Service Packages were created? You should be able to find them in the Records-> Service Package. If the Robot Manager was installed properly, you should find both of these with 7 URI templates listed in the robotics service package and at least 6 URI templates listed for the roboticsSSO service package. They should also be utilizing the latest Pega-Robotic-AutomationPackageManagement that you have installed. This may be a place to start.
Yes, your robot should hit robotics SSO, but this should be possible through adding in certain privileges to your application. Your config files will still only need the /api/v1 server urls. For example, you will have to have the Pega Robotic Automation Console added as a built on application to your application definition. You will also need the PegaRULES:RoboticAdministrator and AutomationPackageManagement:Admin roles added to the access group of the robot operator. If these are already configured and your robot isn't connecting, it may be an issue with the decision tables that are set up to connect the robot user with the application.