the api /ru_to_ac should be prefixed with a custom_code that verifies the data given by the login such that an user can not avoid the login page calling directly the api behind it
this will be resolved from #175 since once it is finished /ru_to_ac will not be callable from the extern since it will be included in the authorize_backend API
the api /ru_to_ac should be prefixed with a custom_code that verifies the data given by the login such that an user can not avoid the login page calling directly the api behind it